Disclosure of Invention
The invention provides a method and a device for managing network management system configuration data, which aim to solve the problem that the existing network management system configuration default value cannot well meet the personalized requirements, so that the network management system cost is high.
In order to solve the above technical problem, the present invention provides a method for managing configuration data of a network management system, which comprises:
creating a configuration record for the network management system;
judging whether a user-defined object default value set for the configuration parameters in the configuration record exists or not; if so, setting the value of the configuration parameter as the default value of the custom object.
In an embodiment of the present invention, before creating the configuration record for the network management system, defining a default value of a custom object;
the default values of the custom object comprise template self-contained default values defined by a user in a data template for the configuration parameters and non-template default values defined by the user directly for the configuration parameters.
In an embodiment of the present invention, determining whether there is a custom object default value set for the configuration parameter in the configuration record includes:
when the configuration record is imported and created in a data template mode and a template self-contained default value exists in the data template, setting the value of the configuration parameter as the template self-contained default value;
if the configuration record is not imported and created in a data template mode, or the configuration record is imported and created in the data template mode but no template self default value exists in the data template, judging whether a non-template default value imported for the configuration parameter exists in a network management system, and if so, setting the value of the configuration parameter as the non-template default value.
In an embodiment of the present invention, before creating the configuration record for the network management system, a default value of a system built-in object is defined;
when the judging result of judging whether the non-template default value imported for the configuration parameter exists in the network management system is non-existent, the method further comprises the following steps:
and judging whether a system built-in object default value set for the configuration parameter exists in the network management system, and if so, setting the value of the configuration parameter as the system built-in object default value.
In an embodiment of the present invention, before creating the configuration record for the network management system, the method further includes defining a database layer and a model layer of the configuration parameters of the network management system;
when the judgment result of judging whether the default value of the system built-in object set for the configuration parameter exists in the network management system is not present, the method further comprises the following steps:
judging whether a database layer and a model layer simple default set for the configuration parameters exist in the system, and if so, setting the values of the configuration parameters as the database layer and the model layer simple default; otherwise, setting the value of the configuration parameter to be null.
In an embodiment of the present invention, after the configuration parameter value of the configuration record is set, further detecting whether a user imports a new non-template default value, if the detection result is yes, performing the following processing:
comparing the value of the corresponding configuration parameter in the system with a non-template default value imported by a user;
and/or updating the values of the corresponding configuration parameters in the system to corresponding non-template default values.
In an embodiment of the present invention, before the determining whether the default value of the custom object set for the configuration parameter exists in the network management system, the method further includes:
and judging whether the user inputs a corresponding parameter value for the configuration parameter, if so, setting the value of the configuration parameter as the parameter value.
In order to solve the above problem, the present invention further provides a device for managing configuration data of a network management system, comprising: a creation module and a management module;
the creating module is used for creating a configuration record for the network management system;
the management module comprises a second setting submodule for judging whether a user-defined object default value set for the configuration parameters in the configuration record exists or not; if so, setting the value of the configuration parameter as the default value of the custom object.
In an embodiment of the present invention, the system further includes a custom default value definition module, configured to define a custom object default value before the creation module creates a configuration record for the network management system; the custom object default values include:
the template defined by the user in the data template aiming at the configuration parameters is provided with a default value and the non-template default value defined by the user directly aiming at the configuration parameters.
In an embodiment of the present invention, the determining, by the second setting submodule, whether there is a custom object default value set for the configuration parameter in the configuration record includes:
when the configuration record is imported and created in a data template mode and a template self-contained default value exists in the data template, setting the value of the configuration parameter as the template self-contained default value;
if the configuration record is not imported and created in a data template mode, or the configuration record is imported and created in the data template mode but no template self default value exists in the data template, judging whether a non-template default value imported for the configuration parameter exists in a network management system, and if so, setting the value of the configuration parameter as the non-template default value.
In an embodiment of the present invention, the system further includes a system built-in default value definition module, which is used for defining a system built-in object default value before the creation module creates a configuration record for the network management system;
the management module further includes a third setting submodule, configured to, when the second setting submodule determines that the non-template default imported for the configuration parameter does not exist in the network management system, determine whether a system built-in object default set for the configuration parameter exists in the network management system, and if so, set the value of the configuration parameter as the system built-in object default.
In an embodiment of the invention, the system further comprises a simple default value definition module, which is used for defining the simple default values of the database layer and the model layer of the configuration parameters of the network management system;
the management module further comprises a fourth setting submodule for judging whether a database layer and a model layer simple default set for the configuration parameters exist in the network management system or not when the third setting submodule judges that the system built-in object default set for the configuration parameters does not exist in the network management system, and if so, setting the values of the configuration parameters as the database layer and the model layer simple default; otherwise, setting the value of the configuration parameter to be null.
In one embodiment of the invention, the device further comprises a detection module, a comparison module and/or an updating module;
the detection module is used for detecting whether a user introduces a new non-template default value after the configuration parameter value of the configuration record is set;
the comparison module is used for comparing the value of the corresponding configuration parameter in the system with the non-template default value imported by the user when the detection result of the detection module is yes;
and the updating module is used for updating the corresponding configuration parameter value in the system to the corresponding non-template default value when the detection result of the detection module is yes.
In an embodiment of the present invention, the management module further includes a first setting sub-module; and the second setting submodule is used for judging whether a corresponding parameter value is input for the configuration parameter by a user before judging whether the self-defined object default value set for the configuration parameter in the configuration record exists or not, and if so, setting the value of the configuration parameter as the parameter value.
The invention has the beneficial effects that:
the network management system configuration data management method and device provided by the invention can define the default value of the user-defined object, and not only is a simple default value defined by a database layer and a model layer; after a configuration record is created for a network management system, judging whether a user-defined object default value set for configuration parameters in the configuration record exists in the system; if yes, setting the value of the configuration parameter as the default value of the custom object. The scheme provided by the invention supports the user to individually define the default value of the configuration parameter, thereby well meeting the flexible customization requirement of different operators on the default value, and not needing to customize different network management versions for different operators, thereby greatly reducing the cost of development and subsequent maintenance and improving the satisfaction degree of user experience.
Detailed Description
The present invention will be described in further detail with reference to the following detailed description and accompanying drawings.
The first embodiment is as follows:
fig. 1 shows a method for managing configuration data of a network management system according to this embodiment, which includes:
step 101: creating a configuration record for a network management system;
step 102: judging whether a user-defined object default value set for the configuration parameters in the configuration record exists in the system; if so, the value of the configuration parameter is set as the default value of the self-defined object.
Therefore, the scheme provided by the embodiment supports the user to perform personalized customization on the default value of the configuration parameter, so that the requirement of different operators for flexibly customizing the default value can be well met, different network management versions do not need to be customized for different operators, and the cost of development and subsequent maintenance can be greatly reduced.
Before the step 101, defined object-level defaults of the configuration parameters of the network management system are included, and the object-level defaults include a custom object default K1 and a built-in object default K2 defined by the network management system. Before the step 101, a database layer and a model layer simple default value K3 for defining the configuration parameters of the network management system are also included; in this embodiment, the simple default values K3 of the database layer and the model layer are simply to define a fixed default value and value range for a parameter. For example, for configuration parameter a, the default value is defined as 5, and the range is defined as 1 to 10; the object-level default value of the configuration parameter in this embodiment may be specifically set according to a value of at least one other parameter associated with the configuration parameter, that is, the object-level default value determines the default value and the range of the configuration parameter according to the other configuration parameter values of the configuration record, and the object-level default value is further divided into the object-level default value of the record and the object-level default value of the cross-record. Examples are as follows:
this record object level default: when the associated configuration parameter B of the configuration record is equal to 100, the default value of the configuration parameter A is defined as 5, and the range is defined as 1-10. When the record associated configuration B parameter is equal to 200, the default value of the configuration parameter A is defined as 10, and the range is defined as 5-10.
Cross-record object level defaults: when a related configuration parameter C of another configuration record is equal to 100, the default value of the configuration parameter A in the configuration record is defined as 5, and the range is defined as 1-10. When the associated parameter C is equal to 200, the default value of the configuration parameter A in the configuration record is defined as 10, and the range is defined as 5-10.
The object-level default value in this embodiment may be compatible with the simple default value definition of the database layer and the model layer, and the object-level default value is changed to the simple default value as long as the association condition of the object-level default value is null.
Specifically, the default value K1 of the custom object in this embodiment includes:
the template defined by the user in the data template for the configuration parameter is provided with a default value K11;
the user directly aims at the self-defined non-template default value K12 of the configuration parameter, and in this embodiment, the non-template default value K12 of each configuration parameter may be specifically placed in one file to form a default value file, so that the user can conveniently import the configuration parameter.
The step 102 of determining whether the default value of the custom object set for the configuration parameter exists in the system includes:
if the configuration record is judged to be imported and created in a data template mode, judging whether a template self-contained default value K11 exists in the data template, and if so, setting the value of the configuration parameter as the template self-contained default value K11;
if the configuration record is judged to be not imported and created in a data template mode, or the configuration record is judged to be imported and created in the data template mode but no template self-contained default value exists in the data template, whether a non-template default value K12 imported for the configuration parameter exists in the network management system is judged, and if the non-template default value K12 exists, the value of the configuration parameter is set to be the non-template default value K12.
In this embodiment, before determining whether there is a default value K1 of the custom object set for the configuration parameter in the system, the method further includes:
and judging whether the user inputs a corresponding parameter value K0 for the configuration parameter, and if the user inputs the parameter value, directly setting the value of the configuration parameter as the parameter value with priority.
That is, in the present embodiment, the determination priorities of the user input parameter K0, the template default value K11, the non-template default value K12, the system built-in object default value K2, and the database layer and model layer simple default value K3 can be flexibly set, and in the present embodiment, the user input parameter K0, the template default value K11, the non-template default value K12, the system built-in object default value K2, and the database layer and model layer simple default value K3 are exemplarily described in order from high to low, where the process is shown in fig. 2 and includes:
step 201: creating a configuration record for a network management system;
step 202: processing each configuration parameter in the configuration record in sequence;
step 203: judging whether the parameter value K0 is input by the user; if yes, go to step 204; otherwise, go to step 205;
step 204: the value of the configuration parameter is set to the parameter value K0 and the process jumps to the end.
Step 205: judging whether the creation configuration record is created by importing creation data in a template mode and whether a template with a default value K11 exists in the template, if so, turning to step 206; otherwise, go to step 207;
step 206: and setting the value of the configuration parameter as the template with the default value K11, and jumping to the end.
Step 207, judging whether a non-template default value K12 imported for the configuration parameters exists in the system, if so, turning to step 208; otherwise, go to step 209;
step 208: the value of the configuration parameter is set to the non-template default value K12 and the process jumps to the end.
Step 209: judging whether a default value K2 of the system built-in object set for the configuration parameters exists in the system, if yes, turning to step 210; otherwise, go to step 211;
step 210: setting the value of the configuration parameter as the default value K2 of the system built-in object; jumping to the end;
step 211: judging whether a database layer and a model layer simple default value K3 set for the configuration parameters exist or not, and if so, turning to step 212; otherwise, go to step 213;
step 212: the values of the configuration parameters are set to the simple default values K3 for the database layer and the model layer, and the process jumps to the end.
Step 213: and setting the value of the configuration parameter to be null, and jumping to the end.
In this embodiment, 3 types of default values, i.e., the non-template default value KK12, the built-in object default value K2, and the database layer and model layer simple default value K3, are effective for the whole network management system, while definition of default values, i.e., the template with default value K11, is effective for the single template importing process, and control of the use range of different default value types provides a more flexible default value use strategy. Further illustration is made by taking one of the cases of importing the template with default value K11 in the above step 206 as an example, and please refer to fig. 3, which includes:
step 301: the user uses the template to import the network management configuration data in batch;
step 302: the template is provided with a parameter value K0 input by a user for some configuration parameters;
step 303: the system sets the value of the corresponding configuration parameter according to the parameter value K0 in the template;
step 304: for configuration parameters for which the user does not input the parameter value K0, the default value customized by the user in the template is used as the standard.
The function shown in fig. 3 can satisfy the requirement of operators to quickly create base station configuration data in batches. The operator would like to use new default definitions for this group of base stations, but would not like to modify the existing default definitions of the system. At which point the operator may write a new default definition into the data template. When the system imports the data templates, only in the current import process, the default values defined by the templates are used, and after the import is completed, the default values of the templates are invalid. The process can simply and temporarily modify the default value definition of the base station, and also does not need to upgrade the network management.
Because the default management of the existing network management configuration system only defines simple default values in a database layer and a model layer, when the existing configuration data of the base station needs to be uniformly modified, the network management version can only be upgraded, and the configuration data of the base station can only be upgraded. This implementation is cumbersome and the implementation cycle is lengthy.
In this embodiment, after configuration parameters of configuration records are set, when upgrading is required, a user may import a default value file, where the file includes a non-template default value K12, and when it is detected that a new default value file is imported, a configured value of a corresponding configuration parameter in the system may be compared with a corresponding non-template default value K12 in the default value file; or updating the configured value of the corresponding configuration parameter in the system to the corresponding non-template default value K12 in the default value file. The updating in this embodiment can be implemented in a way of flushing, and a specific embodiment process is exemplarily described below, referring to fig. 4, which includes:
step 401: a user imports a set of default value files;
step 402: a user selects corresponding base station configuration parameters;
step 403: the user executes comparison operation, namely, the configured value of the configuration parameter is compared with the corresponding non-template default value K12 in the default value file; the system displays the difference between the current base station configuration data and the user imported default value;
step 404: and (3) the user executes the value brushing operation, the user selects the configuration parameters, the value brushing operation is clicked, and the system refreshes the data which is inconsistent with the default value K12 in the configuration data of the base station into the default value according to the definition of the default value.
It can be seen that the above function of this embodiment can also meet the requirement of an operator to quickly modify the default value of the system, and uniformly refresh the existing configuration data of the base station into the default value defined by the operator; the network management does not need to be upgraded, the operation is convenient, the maintenance cost is low, and the efficiency is high.
Example two:
the present embodiment provides a device for managing configuration data of a network management system, please refer to fig. 5, which includes: a creation module 50 and a management module 52; the management module 52 includes a second setting submodule 522;
the creating module 50 is used for creating a configuration record for the network management system;
the second setting submodule 522 is configured to, after the network management system creates the configuration record, determine whether a user-defined object default value K1 set for the configuration parameters in the configuration record exists in the system; if so, the value of the configuration parameter is set to the custom object default value K1.
The device for managing the configuration data of the network management system in this embodiment includes a custom default value definition module 511, which is used to define a custom object default value K1 before the creation module 50 creates a configuration record for the network management system; the defined custom object defaults include:
the template self-contained default value K11 defined by the user for the configuration parameters in the data template and the non-template default value K12 defined by the user directly for the configuration parameters; the second setting sub-module 522 determines whether there is a default value of the custom object set for the configuration parameter in the system, which includes:
if the configuration record is judged to be imported and created in a data template mode, judging whether a template self-contained default value K11 exists in the data template, and if so, setting the value of the configuration parameter as the template self-contained default value K11;
if the configuration record is judged to be not imported and created in a data template mode, or the configuration record is judged to be imported and created in the data template mode but no template self-contained default value exists in the data template, whether a non-template default value K12 imported for the configuration parameter exists in the network management system is judged, and if the non-template default value K12 exists, the value of the configuration parameter is set to be the non-template default value K12.
The device for managing the configuration data of the network management system in this embodiment further includes a system built-in default value defining module 512, configured to define a system built-in object default value before the creating module 50 creates a configuration record for the network management system; the management module 52 further includes a third setting submodule 523 configured to, when the second setting submodule 522 determines that the custom object default value K1 set for the configuration parameter does not exist in the system, determine whether a system built-in object default value K2 set for the configuration parameter exists in the system, and if so, set the value of the configuration parameter as the system built-in object default value K2.
The device for managing configuration data of a network management system in this embodiment further includes a simple default value defining module 513, configured to define a simple default value K3 for a database layer and a model layer of configuration parameters of the network management system;
the management module 52 further includes a fourth setting submodule 524, configured to, when the third setting submodule 523 determines that the built-in object default value K2 set for the configuration parameter does not exist in the system, determine whether a database layer and a model layer simple default value K3 set for the configuration parameter exists in the system, and if so, set the value of the configuration parameter as the database layer and model layer simple default value K3; otherwise, the value of the configuration parameter is set to null.
In this embodiment, the simple default values of the database layer and the model layer are simply to define a fixed default value and a value range for one parameter. The object-level default value of the configuration parameter in this embodiment may be specifically set according to a value of at least one other parameter associated with the configuration parameter, that is, the object-level default value determines the default value and the range of the configuration parameter according to the other configuration parameter values of the configuration record, and the object-level default value is further divided into the object-level default value of the record and the object-level default value of the cross-record. The object-level default value in this embodiment may be compatible with the simple default value definition of the database layer and the model layer, and the object-level default value is changed to the simple default value as long as the association condition of the object-level default value is null.
In this embodiment, the management module 52 further includes a first setting submodule 521; before the second setting sub-module 522 determines whether the default value K1 exists in the system, it determines whether the user has input the corresponding parameter value K0 for the configuration parameter, and if so, sets the value of the configuration parameter to the parameter value KO.
That is, the determination priorities of the user input parameter K0, the template default value K11, the non-template default value K12, the system built-in object default value K2, and the database layer and model layer simple default value K3 are set in order from high to low in the present embodiment. When the judgment is made, the judgment is made in order of the priority.
Because the default management of the existing network management configuration system only defines simple default values in a database layer and a model layer, when the existing configuration data of the base station needs to be uniformly modified, the network management version can only be upgraded, and the configuration data of the base station can only be upgraded. This implementation is cumbersome and the implementation cycle is lengthy.
In this embodiment, after configuration parameters of configuration records are set, when upgrading is required, a user may import a default file including a non-template default value K12, and when it is detected that a new default file is imported, a configured value of a corresponding configuration parameter in the system may be compared with a corresponding default value in the default file; or updating the configured value of the corresponding configuration parameter in the system to the corresponding default value in the default value file. The updating in this embodiment may be implemented in a flush mode. Therefore, referring to fig. 6, the management apparatus for configuration data of a network management system in this embodiment further includes a detection module 55, and a comparison module 53 and/or an update module 54;
the detecting module 55 is configured to detect whether a user has a new default value of a non-template after setting the configuration parameter value of the configuration record;
the comparing module 53 is configured to compare the configured value of the corresponding configuration parameter in the system with the corresponding non-template default value K12 in the default value file when the detection result of the detecting module 55 is yes; namely, the configured value of the configuration parameter is compared with the corresponding non-template default value K12 in the default value file; the system displays the difference between the current base station configuration data and the user imported non-template default value K12;
the updating module 54 is configured to update the configured value of the corresponding configuration parameter in the system to the corresponding non-template default value K12 in the default value file when the detection result of the detecting module 55 is yes. Specifically, the user selects the configuration parameters through the updating module 54, clicks the refresh operation, and the system refreshes the data inconsistent with the template default value K12 in the configuration data of the base station to the default value according to the definition of the default value.
Therefore, the management device for the configuration data of the network management system of the embodiment can also meet the requirement of an operator for quickly modifying the default value of the system, and uniformly refreshes the existing configuration data of the base station into the default value defined by the operator; the network management does not need to be upgraded, the operation is convenient, the maintenance cost is low, and the efficiency is high.
The foregoing is a more detailed description of the present invention that is presented in conjunction with specific embodiments, and the practice of the invention is not to be considered limited to those descriptions. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.