CN113873540A

CN113873540A - Network element configuration data merging method, device, system, electronic equipment and medium

Info

Publication number: CN113873540A
Application number: CN202010619470.1A
Authority: CN
Inventors: 方楷
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2020-06-30
Filing date: 2020-06-30
Publication date: 2021-12-31
Also published as: WO2022001269A1

Abstract

The embodiment of the invention discloses a method, a device, a system, electronic equipment and a medium for merging network element configuration data. The network element configuration data merging method comprises the following steps: loading a pre-configured merging template; acquiring a merging rule according to the merging template; adjusting the configuration data to be combined according to the merging rule; the adjusted configuration data to be merged is merged, so that the merging of the configuration data of the multimode station can be realized in various complicated reconstruction scenes on site, and the efficiency of station merging is improved.

Description

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

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a method, a device, a system, electronic equipment and a medium for merging network element configuration data.

Background

With the popularization of 5G services, operators perform networking construction on the basis of considering old site resources, and improve service processing capabilities of sites, such as processing capabilities of supporting 2/3/4/5G services at the same time. For example, a plurality of old sites are combined into a new site, or more than two opened sites are combined into one site. Site consolidation requires consolidation of site configuration data in consideration of the actual situation of each site.

However, currently, there are many difficulties in merging stations, especially merging station configuration data, which relate to station devices, transmission data and wireless data, and for different reconstruction scenarios in an actual field, rules for merging configuration data are different, and a large amount of parameters and configuration data of the devices need to be modified. When the configuration file is complex and the number of devices is large, a large amount of workload is brought to the merging work of the sites. Therefore, how to realize the merging of the multimode stations under various complex modification scenes on site becomes a problem to be solved urgently.

Disclosure of Invention

One or more embodiments of the present disclosure provide a method, an apparatus, a system, an electronic device, and a medium for merging network element configuration data, which can merge site configuration data in various complex reconstruction scenarios on site, and improve efficiency of site merging.

To solve the above technical problem, one or more embodiments of the present specification are implemented as follows:

in a first aspect, a method for merging network element configuration data is provided, where the method includes: loading a pre-configured merging template; acquiring a merging rule according to the merging template; adjusting the configuration data to be combined according to the merging rule; and carrying out merging operation on the adjusted configuration data to be merged.

In a second aspect, a device for merging network element configuration data is provided, including: the loading module is used for loading a pre-configured merging template; the merging station rule acquisition module is used for acquiring merging station rules according to the merging station template; the adjusting module is used for adjusting the configuration data to be combined according to the station combination rule; and the merging operation module is used for merging the adjusted configuration data to be merged.

In a third aspect, a network management system is proposed, which includes the network element configuration data merging device as described above.

In a fourth aspect, an electronic device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the network element configuration data merging method described above is implemented.

In a fifth aspect, a storage medium for a computer-readable storage is proposed, the storage medium storing one or more programs which, when executed by one or more processors, implement the steps of the network element configuration data merging method as described above.

As can be seen from the technical solutions provided in one or more embodiments of the present specification, in the method for merging network element configuration data provided in the embodiments of the present specification, a pre-configured merging site template is loaded first, the contents of merging site templates corresponding to different merging sites are different, the merging site template includes a network element model version number of the merging site, a network element model of a corresponding version can be found based on the network element model version number, and a merging rule matched with the network element model is correspondingly found, so that the merging rule can be obtained according to the merging site template, and it can be understood that different merging sites can correspond to different template contents, different network element models, and different merging rules. After the merging station rule is found, the configuration data to be merged can be adjusted according to the merging station rule, and the adjusted configuration data to be merged is merged. Different merging sites can adopt different merging rules to adjust the configuration data to be merged and then merge the configuration data. It can be seen that the pre-configured templates are directly loaded when the configuration data are merged, and the merging of the configuration data is accelerated after different merging rules are adopted to adjust the actual conditions of different merging stations, so that the complicated station merging process is simplified, and the merging work efficiency is accelerated.

Drawings

In order to more clearly illustrate one or more embodiments or prior art solutions of the present specification, reference will now be made briefly to the attached drawings, which are needed in the description of one or more embodiments or prior art, and it should be apparent that the drawings in the description below are only some of the embodiments described in the specification, and that other drawings may be obtained by those skilled in the art without inventive exercise.

Fig. 1 is a schematic diagram illustrating steps of a method for merging network element configuration data according to an embodiment of the present invention.

Fig. 2 is a schematic step diagram of another method for merging network element configuration data according to an embodiment of the present invention.

Fig. 3 is a schematic step diagram of a method for merging network element configuration data according to an embodiment of the present invention.

Fig. 4 is a schematic step diagram of a method for merging network element configuration data according to an embodiment of the present invention.

Fig. 5 is a schematic step diagram of a method for merging network element configuration data according to an embodiment of the present invention.

Fig. 6 is a schematic step diagram of a method for merging network element configuration data according to an embodiment of the present invention.

Fig. 7 is a schematic step diagram of a method for merging network element configuration data according to an embodiment of the present invention.

Fig. 8 is a schematic step diagram of a method for merging network element configuration data according to an embodiment of the present invention.

Fig. 9 is a schematic step diagram of a method for merging network element configuration data according to an embodiment of the present invention.

Fig. 10 is a schematic structural diagram of a device for merging network element configuration data according to an embodiment of the present invention.

Fig. 11 is a schematic structural diagram of a network management system according to an embodiment of the present invention.

Fig. 12 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Fig. 13 is a schematic diagram illustrating a merging rule definition in another method for merging network element configuration data according to an embodiment of the present invention.

Fig. 14 is a schematic diagram of merging station template definition in another network element configuration data merging method according to an embodiment of the present invention.

Detailed Description

In order to make the technical solutions in the present specification better understood, the technical solutions in one or more embodiments of the present specification will be clearly and completely described below with reference to the accompanying drawings in one or more embodiments of the present specification, and it is obvious that the one or more embodiments described are only a part of the embodiments of the present specification, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.

The network element configuration data merging method provided by the embodiment of the invention is a method for merging configuration data of station merging stations, can realize merging of the station configuration data under various complex reconstruction scenes on site, and improves the efficiency of station merging. The network element configuration data merging method and the steps thereof provided in this specification will be described in detail below.

It should be noted that the merging site mentioned in the present application may include a migration site and a destination site, and the number of the migration sites is not limited, and may be one or more. The destination site is the site where the finally merged configuration data is deposited and used as the final usage site. The target site may be a newly opened site, or an already opened site that is not in the list of the migration sites, or in the list of the migration sites, and the network element configuration data merging method provided by the present application is applicable to both.

Example one

Fig. 1 is a schematic step diagram illustrating a method for merging network element configuration data according to an embodiment of the present invention. It can be understood that, in the network element configuration data merging method provided in the embodiment of the present invention, the merging station is used as a network element, and the merging method is also applicable to merging of configuration data of network elements, and can solve the problem of merging processing of configuration data between merging stations in various complicated modification scenarios implemented on a merging station site. The network element configuration data merging method comprises the following steps:

step 10: loading a pre-configured merging template;

in the network element configuration data merging method provided in the embodiment of the present specification, a station template and a merging rule set are preconfigured for a station merging station, considering that different modification scenarios may occur in an actual field of the station merging station, where the modification scenarios relate to station equipment, transmission data, and wireless data. The merging station template is the same template, and the contents embodied in the merging station template are different according to different situations of merging stations.

Referring to fig. 14, the merge site template includes the version number of the network element model of the merge site, the merge relationship of the merge site, the storage location of the configuration data of the merge site, and extension information for planning the protocol.

The content of the merging station template comprises relevant information of the merging station, the relevant information of the merging station comprises configuration of a corresponding reconstruction scene, the version number of a network element model of the merging station is configured, a network element model with a corresponding version number can be searched subsequently based on the version number of the network element model, and the network element model and the merging station rule set are configured in a matched manner, so that the merging station rule set corresponding to the merging station can be found after the network element model of the merging station is found, and the configuration data is adjusted according to the merging rule in the merging station rule set. Therefore, the corresponding configuration can be performed according to different modification scenes of the merging station, and the merging template can also plan the equipment, transmission and wireless parameters of the merging station for subsequent adjustment.

The user can plan the merging operation of one or more groups of merging sites under different scenes in the merging template, and a group of merging sites can comprise a migration site and a target site. The merging operation of configuration data of one or more groups of sites of the same target site can be combined into one merging task under the condition of the target site. The multiple parallel tasks can be executed concurrently, and the merging operation of multiple groups of parallel stations in a single parallel task can be serial, that is, only one merging operation of the migration station and the target station is operated at a time, and the merging operation of multiple groups of parallel stations in the single parallel task is completed sequentially.

And loading and analyzing the merging station template by taking the merging station template as input when the merging station task starts, and acquiring relevant information related to the merging station. In order to improve the station combining efficiency, the stations performing the station combining operation in the station combining task may belong to the same network element model version.

Step 20: acquiring a merging rule according to the merging template;

as mentioned above, after the network element model version number of the merging station is obtained according to the merging station template, the network element model corresponding to the version number can be found, and the network element model and the merging station rule set are configured in a matching manner, so that the network element model and the merging station rule set corresponding to the merging station are obtained through analysis after the network element model packet corresponding to the model version number of the target station is loaded.

The merging station rule set is pre-configured based on different network element models, and as the name suggests, the merging station rule set comprises a plurality of merging station rules. The configuration data may be uniformly combined according to the merging rule, the merging rule selects the same merging rule, the configuration data may be adjusted by the merging rule as mentioned in the following step and then the adjusted configuration data is merged, the management units in the configuration data may be merged one by one, and the management units in the configuration data may be respectively adjusted and then merged one by one.

Step 30: adjusting the configuration data to be combined according to the merging rule;

inquiring the configuration data to be combined of the merging station, adjusting the configuration data to be combined, searching merging rules of corresponding scenes in a merging rule set according to merging scenes configured in a merging station template, adjusting the configuration data of the merging station if the merging rules are found, and defaulting that the configuration data of the merging station is not combined if the merging rules are not found.

Before merging, the configuration data of the merging station needs to process conflicts among the configuration data, such as conflicts of data identification IDs, ID conflicts of corresponding adjustment wireless services of the configuration data with an association relationship, and the like, and also relates to the conditions of replanning or adjusting station equipment, transmission parameters, and the like, so that merging operation needs to be performed after the configuration data to be merged are adjusted by adopting a merging rule.

It will be appreciated that copies of the configuration data from the site are placed in the editing area of the configuration and retained in the original area before the adjustment is made. The adjustment is performed only by operating the configuration data of the editing area.

Step 40: and carrying out merging operation on the adjusted configuration data to be merged.

And merging the adjusted configuration data to be merged, thereby smoothly merging the configuration data of different merging stations to the target station. Therefore, before the merging operation, the configuration data of the merging station is adjusted, so that the situations of conflict in the merging process and configuration data confusion after merging are avoided, the efficiency of merging the configuration data of the merging station is improved, and the labor and time cost are saved.

Referring to fig. 2, in some embodiments, in the network element configuration data merging method provided in this embodiment of the present specification, the configuration data to be merged includes a site management object, and step 30: adjusting the data to be combined according to the merging rule, specifically comprising:

step 300: and adjusting the site management object according to the site merging rule, wherein the site merging rule corresponds to the granularity of the site management object one by one.

In a mobile communication system, particularly in a 5G cellular mobile communication system, a model driver supports the operation of the entire mobile communication system, and each service defines its own model based on a cell model. In the network element model, a service defines a dependency relationship between site management objects MO and an association relationship of the service. Based on this, the merging rule defines the specification to which the adjustment action follows, and each service of the merging site executes the merging rule according to the specification in the network element model according to the granularity of the site management object MO, that is, one site management object MO is adjusted by one merging rule, and then executes the merging operation according to the granularity of the site management object MO.

The adjustment of the site management object MO according to the merging rule mainly includes conflict processing, such as conflict of site management object identifiers MOID and ID conflict of wireless services, and then merging configuration data of the migration site to the target site. In addition, merging of the merging stations also relates to the situation that equipment, transmission parameters and the like of the merging stations need to be re-planned or adjusted, and after the cell number of the station side radio is adjusted, the cell number which is consistent with the cell information of the controller side, such as the cell number of the GSM, needs to be considered.

Referring to fig. 13, as an example one, each of the merging rules includes a merging rule definition XML file and a running algorithm LUA script file of the merging rule. The operation algorithm of the merging rule in this example is to perform merging operation on the site management object immediately after adjusting one site management object, and to complete the adjustment and merging operations of the site management object in sequence.

Example 1

And storing the merging station rule set in a network element model packet, wherein each merging station rule comprises an XML file defined by the merging station rule and an LUA script file in the merging station rule operation algorithm.

(1) The merge rule defines the XML file name: xml, encoded in UTF-8 format.

Such as: /home/model/CUDU/V1.10.30.00B06_ ITRAN02B07 built 27/brs/cm/merge/NRNeigh borreiation-mergeRules.xml;

the site rule definition XML file includes the following information:

ruleId: the serial number of the rule is unique in the site of the site combination, and the naming rule is as follows: MG-realm-NFC name-serial number,

such as "MG-Radio-ncs-1001".

mergeMoc: currently, a merged site management object MO definition is processed, only one migration object is configured for one rule, and a value taking needs to be performed on a full path with a network element model, such as "/managed element/Equipment/RfLink".

dependency: the related moc definition of the dependency in the operation algorithm of the merge operation can define the objects on which a plurality of operation algorithms depend. Taking values requires taking the full path of the network element model, such as:

"/ManagedElement/Equipment/ReplaceableUnit/RfPort"。

relationship index: the object attribute field of the current migration process contains the reference of the incidence relation, and a plurality of relationship index items are defined. Such as "/ManagedElement/Transport/sctp; ManagedElement/Transport ".

The error: and self-defining an error prompt statement. A number of Error messages may be defined, with hint levels including Critical, Error, and Warn.

arithmetic: the definition of the merging rule operation algorithm can define the merging rule operation algorithm of a plurality of migration scenes.

extension: static extension parameters of the merge rule are defined.

(2) The file name of the LUA script file of the merging station rule operation algorithm is named as default according to the ruleId in the XML file of the definition file of the merging station rule, and the name is as follows: and if the rulId defined by the merging station rule is MG-Radio-ncs-0001, the LUA script file name corresponding to the merging station rule is defaulted to be MG-Radio-ncs-0001. LUA. The LUA script file is stored in a LUA subdirectory under the current directory of the xml file of the definition file of the merging rule by default, such as:

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

when a site management object MO has multiple merging scenes, a soldier-site rule can define LUA script files of the multiple merging scenes, and the script file naming rule is as follows: MG-realm-NFC name-sequence number-context type, such as "MG-Radio-ncs-1001-1. lua". When one LUA script can simultaneously support multiple parallel station scenes, the serial numbers of the multiple parallel station scenes are connected by an underscore "_", such as "MG-Radio-ncs-1002-2_3. LUA.

Referring to fig. 3, in some embodiments, in the network element configuration data merging method provided in the embodiment of the present specification, step 30: adjusting the site management object according to the site merging rule, specifically comprising:

step 310: and sequentially adjusting the site management objects according to the execution sequence of the site management objects until all the site management objects are adjusted.

The subsequent merging operation performed according to the granularity of the site management object MO may be that the merging operation is performed on the site management object immediately after each adjustment of the site management object. Or after all the site management objects complete the adjustment action, the merging operation may be uniformly executed according to the granularity of the site management object MO.

The execution order of the site management object MOs may be determined according to the priority sequence of the association relationship between the site management object MOs of the merging site.

The association relationship between the site management objects MO may define, in the network element model, a dependency relationship between the site management objects MO and an association relationship of the service, for example, a relationship between the site management objects has a parent-child relationship and a reference relationship, and these may be read from the network element model. And defining business relations and algorithm dependency relations in an xml file of the merging rules according to the read association relations in the network element model.

Referring to fig. 4, in some embodiments, the site management object is a site management object of a current merging site, and step 310: the method for merging network element configuration data provided in the embodiment of the present specification further includes:

step 320: judging whether a next station merging site exists or not;

if so, go to step 330: and after the site management object included by the next site merging site is adjusted according to the merging rule, returning to the step of judging whether the next site merging site exists or not until the adjustment of the configuration data of all the site merging sites is completed.

And when the merging station task comprises a plurality of groups of migration stations, after the merging operation of the configuration data of one migration station is completed, continuing to execute a second migration station in the merging station task until all the migration stations in the merging station task complete the merging operation of the configuration data.

The merging task may be an atomic operation, and the merging task is successful only after the configuration data merging operation of all the migration sites in the merging task is successfully completed.

Referring to FIG. 5, in some embodiments, step 310: before sequentially adjusting the site management objects according to the execution order of the site management objects, the method for merging network element configuration data provided in the embodiment of the present specification further includes:

step 50: acquiring a network element model and a merging rule set corresponding to a merging station;

as mentioned above, according to the station merging module, the network element model corresponding to the station merging station and the station merging rule set matched with the network element model are obtained, and the station merging rule set is a set and includes the station merging rule corresponding to the station management object in the network element model.

Step 60: and generating an execution sequence of the site management objects based on the network element model and the station combination rule set.

The association relationship of the site management object MO can be generated according to the network element model and the merging rule set, and then a priority sequence of the association relationship is formulated, and then the execution sequence of the site management object is determined according to the priority sequence of the association relationship.

Referring to fig. 6, in the network element configuration data merging method provided in the embodiment of the present specification, step 50: on the premise of obtaining a network element model corresponding to a merging station and a pre-configured merging rule set, step 20: acquiring a merging rule according to the merging template, which specifically comprises the following steps:

step 200: and acquiring a merging rule corresponding to the site management object from the merging rule set according to the merging template.

The station merging rule set is configured in a matching way corresponding to the network element model, and comprises a station merging rule corresponding to each station management object. And recording the version number of the network element model of the merging station in the merging station template, and finding the corresponding network element model according to the version number of the network element model, so that the merging rule set corresponding to the network element model can be found.

Referring to fig. 7, in some embodiments, in the network element configuration data merging method provided in the embodiment of the present specification, step 60: generating an execution sequence of the site management object based on the network element model and the site merging rule set, specifically comprising:

step 600: generating an association relation between site management objects based on the network element model and the site merging rule set;

in the network element model, the service defines the dependency relationship between the site management objects MO and the association relationship of the service, for example, the relationship between the site management objects includes a parent-child relationship and a reference relationship, which can be read from the network element model. And defining business relations and algorithm dependency relations in an xml file of the merging rules according to the read association relations in the network element model.

Step 610: and determining an execution sequence according to the priority of the incidence relation.

After the incidence relation of the site management object MO is determined, a priority sequence of the incidence relation is established, and a strategy for establishing the priority is as follows:

(1) and the father site management object MO in the network element model is processed preferentially than the sub-site management object MO.

(2) The referenced site management object MO in the network element model is processed preferentially over the referenced site management object MO.

(3) And the site management object MO referred by the service association relation in the network element model is processed preferentially over the referred site management object MO.

(4) The site management object MO depending on the query in the site combination rule algorithm is processed preferentially over the site management object MO currently executing the combination operation.

Referring to fig. 8, in some embodiments, the network element configuration data merging method provided in this embodiment of the present specification includes: on the premise of generating the association relationship between the site management objects based on the network element model and the merging rule set, step 30: adjusting the configuration data to be merged according to the merging rule, specifically comprising:

step 340: when the site management object identifier of one of the site management objects is adjusted, the association adjustment is performed on other site management objects of the site management object associated with the one of the site management objects according to the association relationship.

During adjustment, association adjustment can be performed on the identifiers of the associated site management objects, for example, adjustment related to the identifiers MOIDs of the site management objects, the identifiers of the associated other site management objects MO can be automatically associated and adjusted according to the parent-child relationship, the reference relationship and the business association relationship of the site management objects MO in the network element model, and adjustment of the identifiers MOIDs of the site management objects MO is not considered any more when the subsequently associated site management objects MO are adjusted. And performing association processing on conflicts of service id, reference fields and the like of the site management object according to the association relationship.

Referring to fig. 9, in some embodiments, step 40: after performing a merging operation on the adjusted configuration data to be merged, the method for merging network element configuration data provided in the embodiment of the present specification further includes:

step 70: and further adjusting the configuration data after the merging operation in the configured work area.

And further adjusting the configuration data after the merging operation is finished, and ensuring the normal and smooth use of the configuration data of the target station.

After the merging task is successfully completed, if the target station is opened, the target station configuration data which is subjected to merging operation is compared with the target station configuration data of the original area in a difference mode, incremental change and the target station configuration data are written into a working area configured by the network management system, and a user can further adjust the target station configuration data in the working area, such as validity check, data activation and the like. If the target station is not opened, the configuration data of the target station is imported into a virtual station created by the network management system, and a user can further adjust the configuration data of the target station in a working area, such as compliance with legitimacy constraint after data combination, offline legitimacy check, data export opening and the like.

Example two

The following is an example two of performing a station merging operation by using the network element configuration data merging method provided by the present application, where a target station is already opened.

1. Presetting conditions:

(1) after the SRD is converted into ITRAN, an ITRAN site A is not opened, the subnet number is 135797531, the network element ID is 5551, the version of the network element model is V1.0, and the opening mode is GSM/UMTS/LTE/NB;

(2) an ITRAN site B is opened in the current network, the subnet number is 135797531, the network element ID is 5552, the network element model version is V1.0, and the opening standard is NR;

2. task execution

Step 1: filling out a site merging template, including site configuration information (SiteCfg) and extended planning adjustment information (× extensinfo), wherein the information of the site configuration (see fig. 14) includes:

(1) the working scene is as follows: station scene [1000]

(2) A work sub-scenario: default scene [1000]

(3) The network element ID of the transfer station: 5551

(4) URL stored in the data of the migration station:

ftp://ManagedElementType＝ITBBU,SubNetwork＝135797531,ManagedElement＝5551

note: ftp represents a data source that is offline and is stored on an ftp server.

(5) URL stored in the destination station data:

pca://ManagedElementType＝ITBBU,SubNetwork＝135797531,ManagedElement＝5552

note: pca stands for online site, stored in a configured workspace.

Step 2: and establishing a merging task, importing a merging template, associating a working area AAA, storing and executing.

And step 3: analyzing the merging template, reading the information of the migration station A and the target station B, and merging the station operation expansion planning adjustment information.

And 4, step 4: and loading the model information and the merging rule set of the site management object MO in the network element model packet V1.0.

And 5: and generating an execution sequence of the adjustment and combination operations of the site management object MO in the network element model V1.0 version in the default site merging scene according to the model information and the definition information of the site merging rule.

Step 6: and inquiring the data of the target station B to the working area, copying two copies of the configuration data of the target station and respectively storing the two copies of the configuration data in the editing area and the original area.

And 7: downloading the configuration data of the migration site A from the FTP server, inquiring the configuration data of the migration site A, executing the operation of adjusting and combining the site management object MO according to the execution sequence of the adjustment operation of the site management object MO in the network element model, and executing the station combination operation algorithm of the site management object MO.

And 8: after the merging of the configuration data of the migration station A is completed, judging whether a second migration station exists, if so, continuing to execute the second migration station; if not, the merge task is considered complete.

And step 9: after the merging task is completed, if the merging task is successfully merged, the difference between the target station configuration data of the editing area and the target station configuration data of the original area is compared, the read-only field is filtered, and the incremental change is written into the associated work area AAA of the merging task.

Step 10: the user further adjusts the configuration data of the site B in the working area AAA, such as Master refresh, frequency shift adjustment, and the like.

Step 11: the user performs a validity check of site B in the working area AAA, such as restricting the validity problem, to perform fine-tuning.

Step 12: and the user AAA executes the activation of the configuration data of the site B in the working area to complete the station combining operation.

Example three

The following is an example three of performing a station merging operation by using the network element configuration data merging method provided by the present application, where a target station is already opened.

1. Presetting conditions:

(1) after the SRD is converted into ITRAN, an ITRAN site A is not opened, the subnet number is 135797531, the network element ID is 5551, the version of the network element model is V1.0, and the opening mode is GSM \ UMTS \ LTE \ NB;

(2) newly opening configuration data for manufacturing an ITRAN site C, wherein the configuration data is not opened, the subnet number is 135797531, the network element ID is 5553, the version of a network element model is V1.0, and the opening standard is NR;

2. parallel task execution

Step 1: filling a site merging template, including site configuration information (SiteCfg) and extended planning adjustment information (_ extensinfo), wherein the site configuration information includes:

(1) the working scene is as follows: station scene [1000]

(2) A work sub-scenario: default scene [1000]

(3) The network element ID of the transfer station: 5551

(4) URL stored in the data of the migration station:

ftp://ManagedElementType＝ITBBU,SubNetwork＝135797531,ManagedElement＝5551

(5) URL stored in the destination configuration data:

ftp://ManagedElementType＝ITBBU,SubNetwork＝135797531,ManagedElement＝5553

Step 2: and establishing a merging task, importing a merging template, associating a working area BBB, storing and executing.

And step 3: analyzing the merging template, reading the information of the migration site A and the target site C, and merging the operation expansion planning adjustment information.

And 4, step 4: and reading the model information of the site management object MO and the information of the merging rule set in the loading network element model package V1.0.

And 5: and generating an execution sequence of the adjustment and combination operations of the site management object MO corresponding to the network element model V1.0 version in the default site merging scene according to the information of the network element model and the information defined by the site merging rule.

Step 6: and downloading the configuration data of the target station C from the FTP server, inquiring the configuration data of the target station C, storing the configuration data of the target station C in a working area, copying two parts of the configuration data of the target station C, and storing the copied two parts of the configuration data of the target station C in an editing area and an original area respectively.

And 7: and downloading the configuration data of the migration site A from the FTP server, inquiring the configuration data of the migration site A, executing the adjustment and combination operation of the site management object MO according to the execution sequence of the adjustment and combination operation of the site management object MO corresponding to the network element model, and executing the site combination operation algorithm of the site management object MO.

And 8: after the merging of the configuration data of the migration site A is completed, judging whether a second migration site exists, and if so, continuing to execute the second migration site; if not, the merge task is considered to be completed.

And step 9: after the station combining task is completed, if the task is combined successfully, and the target station is judged to be not opened, the target station data in the editing area is written into the RANDPS of the network management system to create a virtual station C.

Step 10: the user further adjusts the configuration data of the virtual site C in the associated work area BBB, such as Master refresh, frequency shift adjustment, and the like.

Step 11: the user executes offline validity check of the virtual site C, restricts validity problems, and the like in the working area BBB for further adjustment.

Step 12: the user derives configuration data of the virtual site C in the working area BBB.

Step 13: and (4) the user establishes a station C with a data opening flow in the SPU, and the station merging operation is completed.

As can be seen from the above analysis, in the network element configuration data merging method provided in the embodiment of the present specification, the pre-configured merging site template is loaded first, the contents of the merging site templates corresponding to different merging sites are different, the merging site template includes the network element model version number of the merging site, the network element model of the corresponding version can be found based on the network element model version number, and the merging rule matched with the network element model is correspondingly found, so that the merging rule can be obtained according to the merging site template, and it can be understood that different merging sites can correspond to different template contents, different network element models, and different merging rules. After the merging station rule is found, the configuration data to be merged can be adjusted according to the merging station rule, and the adjusted configuration data to be merged is merged. Different merging sites can adopt different merging rules to adjust the configuration data to be merged and then merge the configuration data. It can be seen that the pre-configured templates are directly loaded when the configuration data are merged, and the merging of the configuration data is accelerated after different merging rules are adopted to adjust the actual conditions of different merging stations, so that the complicated station merging process is simplified, and the merging work efficiency is accelerated.

Example two

Referring to fig. 10, a network element configuration data merging apparatus 10 provided in an embodiment of the present invention includes: a loading module 100, a merge rule acquisition module 200, an adjustment module 300, and a merge operation module 400. Wherein:

a loading module 100, configured to load a pre-configured merging template;

A merging station rule obtaining module 200, configured to obtain a merging station rule according to a merging station template;

An adjusting module 300, configured to adjust the configuration data to be merged according to the merging rule;

A merging operation module 400, configured to perform merging operation on the adjusted configuration data to be merged.

In some embodiments, in the network element configuration data combining apparatus provided in this embodiment of the present description, the configuration data to be combined includes a site management object MO, and the adjusting module 300 specifically includes:

and adjusting the site management object according to the site merging rule, wherein the site merging rule corresponds to the granularity of the site management object one by one.

Example 1

(1) The merge rule defines the XML file name: xml, encoded in UTF-8 format.

the site rule definition XML file includes the following information:

such as "MG-Radio-ncs-1001".

"/ManagedElement/Equipment/ReplaceableUnit/RfPort"。

extension: static extension parameters of the merge rule are defined.

In some embodiments, in the network element configuration data combining and setting apparatus provided in this embodiment of the present specification, the adjusting module 300 is further configured to:

and sequentially adjusting the site management objects according to the execution sequence of the site management objects until all the site management objects are adjusted.

EXAMPLE III

Referring to fig. 11, in a network management system 1 provided for the embodiment of the present invention, the network management system 1 includes the network element configuration data merging device 10 as described above, and the network element configuration data merging device 10 may include:

a loading module 100, configured to load a pre-configured merging template;

Example four

Referring to fig. 12, an electronic device provided in an embodiment of the present invention includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor, when executing the computer program, implements the steps of the network element configuration data merging method shown in fig. 1 to 9, and specifically may perform the following steps:

step 10: loading a pre-configured merging template;

Step 20: acquiring a merging rule according to the merging template;

Fig. 9 is a schematic structural diagram of a server 900 according to an embodiment of the present disclosure, which includes, at a hardware level, a processor 920, and optionally an internal bus 940 and a memory 920.

The memory 920 is used for storing programs. In particular, the program may include program code comprising computer operating instructions. The memory may include both memory and non-volatile storage and provides instructions and data to the processor. The Memory 920 may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory, such as at least 1 disk Memory. Of course, the server may also include hardware needed for other services.

The processor 910 reads a corresponding computer program from the non-volatile memory into the memory and then runs the computer program. The processor 910 executes the program stored in the memory. The processor 910 and the memory 920 may be connected to each other by an internal bus 940, and the internal bus 940 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus 940 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one double-headed arrow is shown in FIG. 9, but this does not indicate only one bus or one type of bus. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the processor may be implemented by integrated logic circuits in hardware or instructions in software in the processor. The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also 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, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

In the technical solution of the present specification, the network element configuration data merging method provided in the embodiment of the present specification loads a pre-configured merging site template, where contents of merging site templates corresponding to different merging sites are different, the merging site template includes a network element model version number of the merging site, a network element model corresponding to the version can be found based on the network element model version number, and a merging rule matching the network element model can be correspondingly found, so that the merging rule can be obtained according to the merging site template, and it can be understood that different merging sites can correspond to different template contents, different network element models, and different merging rules. After the merging station rule is found, the configuration data to be merged can be adjusted according to the merging station rule, and the adjusted configuration data to be merged is merged. Different merging sites can adopt different merging rules to adjust the configuration data to be merged and then merge the configuration data. It can be seen that the pre-configured templates are directly loaded when the configuration data are merged, and the merging of the configuration data is accelerated after different merging rules are adopted to adjust the actual conditions of different merging stations, so that the complicated station merging process is simplified, and the merging work efficiency is accelerated.

EXAMPLE five

A storage medium provided in an embodiment of the present invention is a computer-readable storage medium, where one or more programs are stored, and the one or more programs may be executed by one or more processors to implement the steps of the network element configuration data merging method shown in fig. 1 to 9, and specifically may perform the following steps:

step 10: loading a pre-configured merging template;

Step 20: acquiring a merging rule according to the merging template;

In short, the above description is only a preferred embodiment of the present disclosure, and is not intended to limit the scope of the present disclosure. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present specification shall be included in the protection scope of the present specification.

The system, apparatus, module or unit illustrated in one or more of the above embodiments may be implemented by a computer chip or an entity, or by an article of manufacture with a certain functionality. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, 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 a combination of any of these devices.

Computer-readable storage media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

Claims

1. A method for merging network element configuration data, the method comprising:

loading a pre-configured merging template;

acquiring a merging rule according to the merging template;

adjusting the configuration data to be combined according to the merging rule;

and carrying out merging operation on the adjusted configuration data to be merged.

2. The method for merging network element configuration data according to claim 1, wherein the configuration data to be merged includes a site management object, and the adjusting of the data to be merged according to the merging rule specifically includes:

and adjusting the site management object according to the site merging rule, wherein the site merging rule corresponds to the granularity of the site management object one to one.

3. The method for merging network element configuration data according to claim 2, wherein the adjusting the site management object according to the site merging rule specifically includes:

4. The method according to claim 3, wherein the site management object is a site management object of a current merging site, and the site management object is sequentially adjusted according to an execution sequence of the site management object until all the site management objects are adjusted, the method further comprising:

judging whether a next station merging site exists or not;

if so, adjusting the site management object included in the next site merging site according to the site merging rule, and returning to the step of judging whether the next site merging site exists or not until the adjustment of the configuration data of all the site merging sites is completed.

5. The method for merging network element configuration data according to claim 3 or 4, wherein before the site management object is sequentially adjusted according to the execution order of the site management object, the method further comprises:

acquiring a network element model corresponding to the merging station and a pre-configured merging rule set;

generating the execution sequence of the site management object based on the network element model and the merging rule set.

6. The method for merging network element configuration data according to claim 5, wherein on the premise of obtaining the network element model corresponding to the merging station and the pre-configured merging rule set, obtaining the merging rule according to the merging template specifically includes:

and acquiring a merging rule corresponding to the site management object from the merging rule set according to the merging template.

7. The method for merging network element configuration data according to claim 5, wherein the step of generating the execution sequence of the site management object based on the network element model and the site merging rule set specifically comprises:

generating an incidence relation between the site management objects based on the network element model and the merging rule set;

and determining the execution sequence according to the priority of the incidence relation.

8. The method for merging network element configuration data according to claim 7, wherein on the premise that the association relationship between the site management objects is generated based on the network element model and the merging rule set, the method for adjusting the configuration data to be merged according to the merging rule specifically includes:

when the site management object identifier of one of the site management objects is adjusted, performing association adjustment on other site management objects in the site management objects associated with the one of the site management objects according to the association relationship.

9. The method according to claim 1, after the adjusted configuration data to be merged is merged, the method further comprises:

and further adjusting the configuration data after the merging operation in the configured work area.

10. A network element configuration data merging apparatus, comprising:

the template generating module is used for loading a pre-configured merging template;

the merging station rule acquisition module is used for acquiring merging station rules according to the merging station template;

the adjusting module is used for adjusting the configuration data to be combined according to the station combination rule;

and the merging operation module is used for merging the adjusted configuration data to be merged.

11. The device for merging network element configuration data according to claim 10, wherein the configuration data to be merged includes a site management object, and the adjusting module specifically includes:

12. The device for merging network element configuration data according to claim 11, wherein the adjusting module is further configured to:

13. A network management system comprising the network element configuration data merging device according to any one of claims 10 to 12.

14. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the network element configuration data merging method according to any one of claims 1 to 9 when executing the computer program.

15. A storage medium for computer readable storage, the storage medium storing one or more programs which, when executed by one or more processors, implement the steps of the network element configuration data merging method according to any one of claims 1 to 9.