CN101083684A - Communication apparatus batch configuration managerial approach and apparatus - Google Patents

Abstract

The invention discloses a method for batch configuration management of communication equipment, comprising the following steps: describing the configuration data in each communication equipment based on a unified description format; downloading the configuration data described in the communication equipment based on the unified description format; downloading The configuration data is parsed and displayed to the outside world for editing; the configuration data edited by the outside world is uploaded to the selected target communication device; and the target communication device is controlled to load the received configuration data. By adopting the general communication equipment batch configuration management method provided by the present invention, data configuration can be performed on communication equipment in an accurate, efficient, scalable, and off-line manner, which avoids tedious and error-prone manual configuration methods, and improves the efficiency of data configuration. accuracy.

Description

Communication equipment batch configuration management method and device thereof

technical field

The invention relates to configuration management of communication equipment, in particular to a batch configuration management method and device for communication equipment.

Background technique

At present, device configuration management is an important means to maintain the normal and orderly operation of communication devices. It initializes devices and configures data to enable devices to provide normal business services or optimize device performance.

For most network maintenance personnel, it is still a manual process to configure data and modify the configuration of devices. This process is barely competent when maintaining a small number of devices, but for common configuration operations in multiple or entire communication networks Or configuration operations with a large amount of data (such as office data creation, billing data adjustment, batch service loading/unloading, batch account opening, batch card opening, etc.), if the network maintenance personnel still perform configuration operations on each device separately, Or use configuration commands to configure related data one by one (for example, after the number segment is modified, the modification command needs to be executed one by one for each changed number segment), which will lead to a problem of relatively large maintenance tasks and low efficiency. In this case It is necessary to adopt a method of batch configuration of communication devices to solve the problem.

The characteristics of batch configuration data shall at least include one of the following situations:

(1) Configure multiple configuration items for one device at the same time.

(2) Configure one or more configuration items for multiple devices at the same time.

In the prior art, there are mainly two ways to perform batch configuration management on communication devices:

One is to provide network maintenance personnel with a visual batch data processing function based on a human-computer interaction graphical user interface (GUI, Graphical User Interface). On this user interface, some configuration items related to functions on each type of device will be classified. Combined together, the network maintenance personnel can complete the batch data configuration of the device by sequentially executing each configuration command on the interface.

However, the inventors of the present application found in the research process that when using this batch data configuration method to configure data in batches, if the configuration requirements change, the application program needs to be rewritten according to the changed demand information to obtain an updated user interface. It will inevitably limit the application flexibility of this configuration method, that is, the scalability of the configuration function is poor.

At the same time, this batch data configuration method refers to the simultaneous completion of batch configuration of multiple configuration items related to one device, rather than batch configuration of multiple devices at the same time. When faced with data configuration for a large number of devices (for example, ports such as routers and access servers need to be configured during the deployment, upgrade, and cutover of the communication system), users can only perform repeated operations on each device on the interface. The steps are not only cumbersome and inefficient, but also many parameters need to be manually input, and the accuracy of the data is not high.

The other is based on a configuration data export tool to export the default data of the device to a text file for the network maintenance personnel. The network maintenance personnel manually modify the relevant data in the text file and then use the import tool to load it to the device. Loaded into the device's memory, database or configuration file.

However, the inventor of the present application found in the research process that when using this batch data configuration method to configure data in batches, since the configuration file needs to be directly modified, there is no timely data correctness verification, and the user must be familiar with the format and context of the configuration file relationship can be corrected. For some places with strong data correlation, if the configuration is inconsistent, the entire network will be blocked, and once there is an inconsistency in the network, it must be completed by manual inspection. Furthermore, the network maintenance personnel must be online to load the configuration file to the device, and once the loading fails, the process must be repeated manually.

Contents of the invention

The technical problem to be solved by the embodiments of the present invention is to provide a method and device for batch configuration management of communication devices, so as to accurately and efficiently perform batch configuration management of communication devices.

An embodiment of the present invention provides a batch configuration management method for communication devices, including the steps of: describing the configuration data in each communication device based on a unified description format; downloading the configuration data described in the communication devices based on a unified description format; downloading The configuration data is parsed and displayed to the outside world for editing; the configuration data edited by the outside world is uploaded to the selected target communication device; and the target communication device is controlled to load the received configuration data.

The embodiment of the present invention also provides a communication device batch configuration management device, including a configuration data description unit for describing the configuration data in each communication device based on a unified description format; a configuration data download unit for downloading the communication The configuration data described in the device based on a unified description format; the configuration data analysis unit is used to analyze and display the downloaded configuration data to the outside world for editing; the configuration data upload unit is used to upload the configuration data edited by the outside world to the selected target A communication device; a data loading control unit, configured to control the target communication device to load the received configuration data.

The embodiment of the present invention also provides a batch configuration management method for communication devices, including the steps of: downloading configuration data in the communication devices; describing the downloaded configuration data based on a unified description format; parsing and displaying the configuration data described based on the unified description format Editing for the outside world; uploading the edited configuration data to the selected target communication device; controlling the target communication device to load the received configuration data.

The embodiment of the present invention also provides a communication device batch configuration management device correspondingly, including a configuration data download unit for downloading configuration data in communication devices; a configuration data description unit for downloading configuration data based on a unified description format Describe; configuration data parsing unit, used to analyze and display the configuration data described based on the unified description format to the outside world for editing; configuration data upload unit, used to upload the configuration data edited by the outside world to the selected target communication device; data A loading control unit, configured to control the target communication device to load the received configuration data.

The communication device batch configuration management method proposed by the embodiment of the present invention downloads the configuration data on the communication device to the local modification, and then configures it to the target communication device in batches. The tedious and error-prone manual configuration work is avoided, and the accuracy of data configuration is improved.

Description of drawings

Fig. 1 is a flow chart of communication equipment batch configuration management;

Fig. 2 is a block diagram of the content of the configuration data description file;

Fig. 3 is a block diagram of the content of the interface organization description file;

Fig. 4 is a block diagram of the content of the control rule description file;

Fig. 5 is a content block diagram of configuration content description file;

Fig. 6 is a schematic diagram of the tree structure on the left side of the analysis interface;

Figure 7 is a schematic diagram of the table structure on the right side of the analysis interface;

Figure 8 is a schematic diagram of the interface when adding configuration data;

Fig. 9 is a schematic diagram of the interface of the verification result list;

FIG. 10 is a schematic diagram of an interface for target device configuration;

Figure 11 is a flowchart of configuration data upload;

Fig. 12 is a flow chart of performing batch configuration management on devices of the same type and different versions;

Fig. 13 is a flow chart of device configuration data upgrade;

FIG. 14 is a schematic structural diagram of an apparatus for batch configuration management of communication equipment proposed by an embodiment of the present invention;

FIG. 15 is a schematic structural diagram of another communication device batch configuration management device proposed by an embodiment of the present invention.

Detailed ways

The first technical solution proposed by the embodiment of the present invention is: describe the configuration data in each communication device based on the unified description format; download the configuration data described in the communication device based on the unified description format, and analyze the downloaded configuration data Displaying to the outside world for editing; uploading the configuration data edited by the outside world to the selected target communication device, and controlling the target communication device to load the received configuration data.

A better implementation situation is to use Extensible Markup Language (XML, Extensible Marker Language) to describe the configuration data, generate a configuration data description file, and analyze the configuration item description file described in XML that is downloaded locally to obtain a general visual configuration interface , the network maintenance personnel can edit the configuration operation on the premise that there are perfect prompts and verification functions on the configuration interface, and then select one or more target devices, and upload the data completed by the local configuration to the target devices in the way of resuming upload. First, after preprocessing according to the actual operating environment of the device, the configuration data is actually loaded onto the communication device, thereby completing automatic batch configuration of multiple devices.

The specific implementation manners of the present invention will be described below in conjunction with the accompanying drawings.

Referring to Figure 1, the process of batch configuration management of communication devices is as follows:

Step 101: Describe the configuration data in each communication device based on a unified description format, that is, use a common data description method to describe the configuration data, and generate a configuration data description file.

In communication devices, configuration data is usually stored in the form of ordinary text files, memory tables or databases, and management information bases (MIB, Management Information Base). But no matter what the form is, it can be roughly divided into the configuration data content part and the data description part, and the latter is usually called a data dictionary. In the data content part, it is usually stored in the form of a two-dimensional relational table; in the data dictionary part, it describes the storage location of the data corresponding to each configuration item, the data type of the field, the value range constraint, business logic, etc. If a device needs a certain record during operation, the corresponding data content can be found according to the description of the data dictionary.

In order to generate a general-purpose configuration data description file that is easy to edit, view, and process, and to adapt to devices that frequently change configuration items and often need to be upgraded, considering the flexibility and scalability of the configuration data description file, the embodiment of the present invention uses an XML file to describe.

Since the communication system can be configured in the order of product-device type-device version-configuration item, the data of each configuration item can be represented by a two-dimensional relationship, and each field of the configuration item can be It is described from multiple perspectives such as scope constraints, data types, business logic, and interface display. Therefore, the configuration data on the device can be completely described by describing the configuration sequence, configuration data, and constraints on the configuration data. The present invention uses three XML files to describe configuration data.

Referring to FIG. 2 , the configuration data description file 200 includes three parts: the first part is the interface organization description file 201 ; the second part is the control rule description file 202 ; the third part is the data content description file 203 . The three parts are described in detail below:

The interface organization description file 201 is mainly a description of the organization and display of the configuration items of the communication device on the interface, specifically including the display order and hierarchical relationship of the configuration items. Each product corresponds to an interface organization description file. As shown in FIG. 3 , the interface organization description file 201 is divided into four levels, and the contents in each level are described in sequence according to the order displayed on the interface. The first level is product information 301, including product identification ID, product name and other information; the second level is device type information 302, including device type ID, device type name and other information; the third level is device version information 303, including version ID , version name, etc.; the fourth level is configuration item information 304, including information such as configuration item ID, configuration item name, and whether to display on the interface. In particular, for a virtual configuration item on a directory, specific configuration items can be nested under it. Through these four levels of description, the organization sequence and hierarchical relationship of all configuration items under a product can be described on the interface; in particular, the public configuration of the corresponding device type can be directly linked under the second level of device type information. Items, these configuration items are common to all versions below it.

An example of the interface organization description file 201 is as follows. Among them, product is a product label, which belongs to the first level of product information 301; devtype is a device type label, which belongs to the first level of device type information 302; common is a public configuration label, which is hung under the first level of device type information 302; version is a device version label, belongs to the first level of device version information 303; fun is a configuration item label and belongs to the first level of configuration item information 304. The meanings of other symbols used in XML in the example are: id is the identification attribute corresponding to the above-mentioned levels; disp is the display attribute corresponding to the above-mentioned levels; name is the name attribute corresponding to the above-mentioned levels.

<? xml version = "1.0" encoding = "GB2312"? >

<product id="1" disp="1" name="infoX AAA">

<devtype id="8402" disp="1" name="AAA System">

<common id="1.0" disp="1" name="common configuration">

<fun id="000184020001" disp="1" name="area information configuration"/>

<fun id="000184020002" disp="1" name="Domestic area code configuration"/>

<fun id="000184020003" disp="1" name="International area code configuration"/>

</common>

<version id="1.1" disp="1" name="V100R002C01">

<fun id="000184021002" disp="1" name="BRAS node management"/>

<fun id="000184021003" disp="1" name="PDSN node management"/>

<fun id="000184021004" disp="1" name="Portal node configuration">

<fun id="000184021005" disp="1" name="Access Portal point management"/>

<fun id="000184021006" disp="1" name="User Portal point management"/>

<fun id="000184021007" disp="1" name="Portal Adaptation Point Management"/>

</fun>

</version>

<version id="1.2" disp="1" name="V100R002C02">

<fun id="000184022001" disp="1" name="BRAS node management"/>

<fun id="000184022002" disp="1" name="GGSN node configuration"/>

</version>

</devtype>

</product>

As can be seen from the above example, the interface display relationship between configuration items can be easily described through the interface organization description file 201, and it is easy to expand, such as adding a configuration item, a fun can be added at the corresponding level Tags and corresponding attributes; deleting a configuration item can delete the corresponding tag. In the same way, it is very convenient to add and remove a device type and device version.

The control rule description file 202 is a control description for the correctness of specific configuration fields and interface elements in the communication device, specifically including data correctness control rules and interface display control rules. Each configuration item corresponds to a control rule description file. As shown in FIG. 4 , the control rule description file 202 includes two parts, one part is a configuration item control description 410 , and the other part is an interface element control description 420 . The configuration item control description 410 is divided into four levels: the first level is the overall control description 411 of the configuration item, including the configuration item ID, whether there is an index, the ID of the parent configuration item, and whether it is a leaf on the configuration item function tree interface Information such as node, whether to display, configuration item description, page verification program, etc.; the second level is the data table description 412, which is mainly the display type of the table on the interface, such as horizontal display according to the order of fields, vertical display of fields, etc.; third Level is the field control description 413, mainly interface display control, data correctness verification rules, etc., specifically including field ID, name, object identifier (OID, ObjectIdentifier), data type, value range, access authority, interface Whether to display, edit box type (such as text box or drop-down box, etc.), edit box interface display size (in pixels), whether it is a primary key, default value, whether it is required, prompt information (Tips), associated to sub The field ID in the table, the verification rule of the button, the verification rule when submitting, whether the edit box is initially activated, whether other columns can be activated, the conditions for activating other columns, the activated field ID, and the type of value that cannot be repeated (in The only one within a device or the only one in the entire communication network, etc.), if the value comes from other configuration rules, give the value rule, if it is a string, give the formatting rule, if it is a selection box, whether to allow multiple choices, whether to ignore Case, whether newlines are allowed, a set of prohibited characters, and if the corresponding field is not a value but a table, the configuration table ID and other information will be given. The fourth level is the field attribute description 414, which mainly includes the enumeration value mapping relationship corresponding to the field, the automatic generation rule of the field value, and the like. Among them, the interface element control description 420 and the second-level data table description 412 in the above-mentioned configuration item control description 410 are located side by side on the same level, mainly including button ID, button title, button action type, and what needs to be executed after the button is executed. operation etc.

An example of the control rule description file 202 is as follows:

<? xml version = "1.0" encoding = "GB2312"? >

<fun id="000184020003"index="1"pfunid="000184020002"treenode="1"disp="1"desp="standby

  Node basic information configuration "vfycmd="">

<table disptype="leveltbl">

<column id="1"name="standby machine IP address"datatype="IPAdress"datarange=""

         maxaccess = "read-write" disp = "1" edittype = "text" editsize = "22,5"

       key = "1" defaultval = "10.10.10.10" addmust = "1" desp = "Physical of the standby machine

                                                                                            

ctlflag="0"ctlcond=""ctlfield=""exltype="network"getvalrule=""

formatrule="" ignorecap="1" newline="0" forbiddenset="" unit=""

extfunid=″″/>

<column id="2" name="standby WAP connection port"datatype="INTEGER"

       datarange = "1000..9999" maxaccess = "read-write" disp = "1"

     edittype = "text" editsize = "22,5" key = "0" defaultval = "1000" addmust = "1"

DESP = w Port connecting wap ″ RetBlfield = ″ 0 ″ keypress = ″ Integer ″

Subvfy=""initact="1"ctlflag="0"ctlcond=""ctlfield=""exltype=""

Getvalrule=""formatrule=""ignorecap="1"newline="0"forbidset=""

unit=″″extfunid=″″/>

</table>

<buttons>

<button id="1001" title="Modify" actionType="Modify"proc=""/>

<button id="1002" title="Add" actionType="Add"proc=""/>

</buttons>

</fun>

As can be seen from the above example, the interface display, authority control and data validity verification of configuration items can be easily described through the control rule description file, so that the configuration data analysis unit can be used to analyze configuration items easily Editing for the visual interface ensures the correctness of the data.

The data content description file 203 is a description of configuration data values, which is described in a hierarchical form, and the configuration data of each device corresponds to a data content description file. As shown in FIG. 5, the data content description file 203 is divided into four levels. The first level is device information description 501, including device ID, device name, device type, and device version information; the second level is configuration item description 502, including configuration item ID and configuration item name; the third level is row description 503, Including the line number, described in the order of the lines; the fourth level is the field description 504, including the field ID, field name, field value, etc., and the field description is described in the order in which the fields are displayed on the interface.

An example of the data content description file 203 is as follows:

<? xml version = "1.0" encoding = "GB23 12"? >

<dev id="1" name="infoX AAA1" devtype="8402" devversion="3.2.1">

<fun id="000184020003"name="configuration of basic information of standby node">

<row id="1">

<column id="1" name="standby machine IP address"value="10.10.10.11"/>

<column id="2"name="standby WAP connection port"value="1001"/>

</row>

</fun>

</dev>

As can be seen from the above example, the two-dimensional relationship of the configuration data can be easily described through the data content description file 203. The configuration item names and field names in this file are actually redundant information, and the details are related to the control rules. Corresponding information in the description file 202 overlaps, and this information is only available when downloaded to the local data content description file, and actually uploaded to the device does not include this information. The purpose of doing this is to facilitate manual viewing or editing when the data parsing unit is not configured for parsing and displaying.

From the perspective of the three parts included in the configuration data description file 200, the master-slave table in the communication device can be described through the interface organization description file 201, and the actual data is still stored separately. For the relationship description in which a field can be associated with a configuration table through control rules from the slave table, the data in the master table and the slave table are actually stored separately. This brings great flexibility and strong scalability to data description.

It should be noted that the hierarchical levels in the configuration data description file 200 can be reduced or expanded without departing from the description content.

Step 102: download configuration data, download the configuration data on the communication device to be configured to the local client, and use it as a basis for batch configuration data.

The configuration data includes three parts in the configuration data description file 200, and the process of downloading the configuration data is to download these configuration data description files from the device to the client. There are many ways to download configuration data, such as downloading configuration data based on File Transfer Protocol (FTP, File Transfer Protocol), Secure File Transfer Protocol (SFTP, Secure File Transfer Protocol), etc.

Step 103: Parsing the configuration data. In order to facilitate the user to edit and verify the validity of the local client, according to some rules defined in the configuration data description file 200, the configuration data is parsed into a visual interface and displayed. In this visual interface , display configuration data in the form of left tree and right table. Among them, the left tree is displayed hierarchically according to product—device type—device version—device name—configuration item, and the schematic diagram of the left tree is shown in Figure 6.

There is a hyperlink at the configuration item level of the left tree, click the configuration item name, obtain the display information of each field from the corresponding control rule description file 202 according to the ID of the current configuration item and organize it into each column title of the two-dimensional table, and then Obtain the data corresponding to the current configuration item ID from the data content description file 203, assemble the data of all fields into records according to the row number and column number, and display them one by one in the two-dimensional table on the upper right.

For an extended table, that is, a table nested in a field, first find the configuration item ID corresponding to the field, then find the corresponding configuration data content according to the ID, and finally complete the assembly of the two-dimensional table row by row and display in interface. For the master-slave table, that is, one row of records corresponds to a two-dimensional table, the master table is displayed in the upper right half, and the slave table is displayed in the lower right half, each with its own button operation area. The relationship between the slave table and the master table is expressed by the ID of the parent configuration item in the control rule description file 202. Whenever a record of the master table is selected, the corresponding slave table data is displayed below, as shown in FIG. 7 .

On the current editing interface, the user can easily see the content of the data and the relationship between configuration items. If the user wants to modify the data, click the Modify button to enter the modification interface. If the user wants to add data, click the Add button to enter the newly added data. interface. Whether it is an editing interface or an interface for adding data, they will be vertically displayed on the interface field by field according to the definition in the control rule description file 202 . For each field, it will be described horizontally in the order of field name, edit box, field range, type, input constraints, etc., to facilitate user input and improve the accuracy of user editing. The newly added data interface is shown in Figure 8. Show.

Step 104: editing configuration data, that is, the user adds, deletes, and modifies data according to relevant prompts on the interface, so that the input data is what the user desires. There are complete information input prompts for the editing process of configuration data, which can improve the efficiency of editing configuration data.

Step 105: Verify the configuration data, and verify the validity of the data, business relevance, etc. on the editing interface to ensure the correctness of the data.

Data verification is required when the user edits the configuration data and submits it. Specifically include: data type verification, range constraint verification, uniqueness verification, data format verification, data association relationship, business logic verification, etc. After the verification is completed, a list of verification results will be displayed on the interface for the user to confirm and correct, as shown in Figure 9 for details. The content of the verification result list here includes: configuration item name, field name, field value, error message description, etc. According to the cause of the error, the user can return to the editing interface and continue to modify until the configuration is correct.

Step 106: Setting the target communication device. According to the needs of batch configuration, one or more communication devices can be selected as target communication devices for configuration.

After editing all configuration data of a device, the user can select the target device to be configured. The process includes: select the name of a source device whose data has already been configured on the tree of configuration items on the left, and according to the content description file 200 of the configuration data, it will display on the right interface that the device has the same category and version as the source device, and the current user owns the device. The list of target devices with operation rights; the user can also click the name of the device type on the configuration item tree on the left, and according to the configuration data content description file 200, the list of target devices for which the current user has operation rights under the device type will also be displayed on the right interface. See Figure 10 for details, where the user can select one or more target devices according to actual configuration requirements.

Step 107: Set configuration mode. It is to select an appropriate mode to perform configuration operations according to the needs of device configuration. Different configuration modes have different effects on the original data on the device. The configuration mode here includes two ways of overwriting configuration and updating configuration. The overwriting configuration refers to firstly deleting the existing configuration data on the target device, and then completely inserting new data configured by the user. The update configuration refers to updating the original data on the target device with new data, that is, to replace the part of data that is on the target device but has new configuration data; Do not make any changes to that part of the data; do an insert operation on the data that is not on the target device but is in the new data. In addition, some configuration requirements are either fully covered or updated. In such cases, this step is optional. In actual operation, according to the actual configuration needs, the configuration mode can be set for each target device, and the configuration mode can be set for all target devices in sequence.

Step 108: Upload configuration data, that is, a process of uploading source configuration data to target devices in batches according to the target device list and configuration mode set by the user. In the case of multiple target devices, the method of concurrently uploading the configuration data is adopted, and the strategy of resuming the upload of the configuration data is adopted in the process of single uploading of the configuration data. The process of uploading to a target device is shown in Figure 11:

Step 1101: Get the name, IP address, connection port and other information of the target device.

Step 1102: Check whether the running state of the target device is normal. If the device is running abnormally, it indicates that data configuration cannot be performed at present, and step 1102 is repeatedly executed.

Step 1103: If the device is running normally, read the breakpoint information when the last upload was interrupted as the starting point for uploading configuration data.

Step 1104: Establish a connection with the target device.

Step 1105: Upload configuration data.

Step 1106: If the upload process is interrupted due to a problem with the target device, save the breakpoint information of this upload, and then go to step 1101 to continue execution; if there is no problem with the target device during the upload process, go to step 1107 Continue to execute.

Step 1107: Check whether all the configuration data has been uploaded, if so, the uploading process ends, otherwise go to step 1105 and continue to execute.

This process of uploading data enables the embodiment of the present invention to realize offline configuration of the device, even when the device is disconnected, it can automatically detect and complete the upload according to the situation, which greatly reduces the degree of manual intervention and improves the efficiency of configuration management. automation.

Step 109: Preprocessing configuration data. Preprocess the configuration data uploaded to the target communication device according to the actual operating environment of the communication device, including data consistency verification, data conversion, resource application, memory or database preprocessing, etc., and convert the configuration data to the device operating environment Operation commands, decomposing configuration data files into several different configuration files and converting them to internally required formats, etc., in order to ensure the consistency and correctness of data in the actual environment.

This step is a preprocessing operation inside the target communication device, which helps to find potential problems before actually implementing the configuration data, reduces the time required for the configuration operation, and ensures the success of the configuration operation.

Because the distributed configuration data usually involves multiple functional components, its logical structure and association relationship are complex and difficult to locate. If the implementation fails, it will increase the complexity of network maintenance. After step 109 is finished, a preprocessing report is output to the user for analysis and viewing. The content of the preprocessing report mainly includes: configuration item name, field name, field value, error message description, repair suggestion, etc. If the preprocessing results are all correct, it will directly prompt that the preprocessing is successful, otherwise, download the preprocessing report to the user for viewing, and the user can re-download the configuration data description file of the device according to the cause of the error and the repair suggestion, and edit it or directly return to the editing interface to continue Modify until the configuration is correct. In particular, in some configuration scenarios where the configuration data does not involve memory allocation, resource application, or database update, the above preprocessing operation may not be required, and this step is optional in this case.

Step 110: Loading configuration data, that is, controlling the target communication device to actually load the successfully preprocessed configuration data, so as to complete the data configuration operation.

Divide the configuration data into configuration files corresponding to different functional components inside the communication device, and format it into the format required internally; thus complete the addition, deletion, modification of data of the managed objects inside the communication device, and the configuration The data is converted into actual run commands etc. After the configuration data is loaded, the communication device can operate according to the new configuration state.

In the following two common situations of network communication device configuration, the process of data configuration using the present invention is given.

1. Batch data configuration of different versions of the same type of communication equipment to adapt to the phenomenon and needs of coexistence of different versions of communication equipment on the live network. For example, in a communication system, two versions of infoX AAA equipment exist at the same time, one is a low version and the other is a high version, and these two versions have most of the same configuration items. At this time, it is not necessary to configure the configuration items for each version from beginning to end. The specific steps are shown in Figure 12: first, the editing and verification of the public configuration data of different versions are completed uniformly; then the editing and verification of the respective configuration data of different versions are completed respectively; the communication device of the same type and different version is set as the target communication device; Set the configuration mode of the target communication device of the corresponding version; then perform batch upload, preprocessing, and loading of configuration data. At this point, all the configuration items of the communication devices of different versions of the same communication device are configured.

2. Upgrading of the configuration data of the communication equipment to meet the changing needs of the configuration data of the communication equipment. For example, in a communication system, upgrade infoX AAA equipment from a lower version to a higher version. The specific steps are shown in Figure 13:

Step 1301: Initialize the parameter type that represents the type of change from a higher version to a lower version, and assign type=0, when type=0, it indicates that there is no version upgrade;

Step 1302: Compare the high version with the low version, and determine whether the configuration items or fields of the low version are deleted. If not deleted, then directly go to step 1304 for execution;

Step 1303: If the higher version has deletions compared with the lower version, delete the data that exists in the configuration content of the lower version but is unnecessary for the higher version, and convert it into a content file of the higher version. Set type=1, then go to step 1304 to continue execution;

Step 1304: Comparing the high version with the low version, it is judged whether several new configuration items have been added or there are newly added fields or new data records in the original configuration items. If the high version does not increase compared with the low version, then directly go to step 1306 for execution;

Step 1305: If there is an increase in the high version compared with the low version, then according to the interface organization file and control rule description file of the high version, the content of the configuration data in the low version is not included, but the configuration data in the new version is empty or missing. After the provincial value is filled, it is converted to the configuration data of the higher version. Set type=2; Then go to step 1306 and continue to execute;

Step 1306: If there are both high and low versions of the configuration item, determine whether the validity control rules such as field ranges and data types in the configuration item in the high version have changed compared with those in the low version. If there is no change, directly go to step 1308 for execution;

Step 1307: If the validity control rules such as field range or data type in the configuration items with the same high version and low version have changed, then directly modify the data content file, and modify the changed data according to the constraints and rules of the new version , so that it meets the description of interface organization and control rules of the high version; set type=3, and then go to step 1308 to continue execution;

Step 1308: Judging whether there is a version upgrade, that is, judging whether type is equal to 0, if yes, go to step 1312 to end the upgrade operation; if not, go to step 1309 to continue execution.

Step 1309: Determine whether the type type is only a deletion of the higher version than the lower version, that is, determine whether the type is equal to 1, if not, go to step 1310 to continue execution, if yes, go to step 1311 to execute;

Step 1310: Analyze the data content file after modifying the lower version configuration data content file according to the higher version, and convert it into a visual interface to edit and verify configuration items;

Step 1311: Set the corresponding target communication device and configuration mode, upload the configuration data file, perform preprocessing of the data file, and actually load the configuration data after the preprocessing is successful, so that the updated communication device runs under the new version.

Step 1312: The configuration data upgrade process ends.

According to the embodiment of the technical solution of the present invention, the present invention here provides a communication device batch configuration management device implementing the technical solution. As shown in FIG. 14, the communication device configuration batch management device includes:

Configuration data description unit 141: used to describe configuration data in each communication device based on a unified description format, which can be described based on but not limited to three parts: interface organization file, control rule file, and data content description file. A preferred implementation mode is to describe the configuration data in the communication device by using the general XML language.

Configuration data downloading unit 142: for downloading configuration data described in the communication device based on a unified description format.

Configuration data parsing unit 143: for parsing and displaying the downloaded configuration data to the outside world for editing.

Configuration data verification unit 144: used to verify the configuration data edited by the outside world, and provide the verification result information to the outside world.

Configuration data uploading unit 145: for uploading configuration data edited by the outside world to the selected target communication device. When uploading, the corresponding data content contained in the configuration data edited by the outside world can be uploaded to the target communication device according to the configuration mode selected in advance for the target communication device. A better implementation mode is that if an interruption occurs during the uploading of configuration data, the unuploaded configuration data will continue to be uploaded from the interrupted point next time.

Configuration data preprocessing unit 146: used for preprocessing the configuration data uploaded to the target communication device according to the current actual operating environment of the target communication device, and providing preprocessing result information to the outside world.

Data loading control unit 147: used to control the target communication device to load the received configuration data; preferably, the data loading control unit 147 controls the target communication device to load the pre-processed configuration data after the above pre-processing is successful.

The configuration data checking unit 144 and the configuration data preprocessing unit 146 in the communication device batch configuration management device are optional. Each functional unit mentioned in the above device can be realized based on software programming, and can also be realized based on modifying existing hardware devices.

The first technical solution introduced above is applicable to the configuration data in each managed communication device in the communication system, which has been described based on a unified description format. However, in the actual network system, there may be some original The configuration data in the communication device has not been upgraded, that is, the configuration data in some original communication devices has not been described using a unified description format. In order to achieve the purpose of the present invention, a second solution is proposed here. Specifically: download the configuration data in the communication device; describe the downloaded configuration data based on the unified description format; analyze and display the configuration data described based on the unified description format to the outside world for editing; upload the configuration data edited by the outside world to the selected the target communication device; controlling the target communication device to load the received configuration data. The downloaded configuration data is described based on three parts: interface organization description file, control rule description file and data content description file. In addition, for details of other technical implementations, please refer to the relevant descriptions of the above-mentioned first technical solution.

As shown in FIG. 15 , in order to correspond to the second technical solution proposed above, a schematic structural diagram of a batch configuration management device for communication equipment proposed in the embodiment of the present invention specifically includes:

Configuration data downloading unit 151: for downloading configuration data in the communication device.

Configuration data description unit 152: used to describe the configuration data downloaded by the configuration data download unit 151 based on a unified description format. The description can be performed based on but not limited to three parts: interface organization file, control rule file, and data content description file describe. A preferred implementation mode is to describe the configuration data in the communication device by using the general XML language.

The configuration data parsing unit 153 is configured to parse and display the configuration data described by the configuration data description unit 152 based on the unified description format to the outside world for editing.

Configuration data uploading unit 154: for uploading configuration data edited by the outside world to the selected target communication device.

Data loading control unit 155: used to control the target communication device to load the received configuration data.

For other relevant implementation details of the device, please refer to the introduction of the working principle of the device shown in FIG. 14 above.

The communication device batch configuration management method proposed by the embodiment of the present invention uses XML to describe the configuration data, and generates a general configuration data description file that is easy to edit, view, and process. By using this file, a visual user interface can be easily parsed, and the network Maintenance personnel have a complete prompt function and data verification function when editing configuration on the visual interface, which ensures the accuracy of data configuration. In addition, due to the flexibility and expansibility of the configuration file, it can adapt to communication devices whose configuration items change frequently and often need to be upgraded.

The communication device batch configuration management device and the target communication device adopt the method of directly transmitting configuration data files instead of issuing configuration commands one by one, which improves the efficiency of communication device configuration. Therefore, it can be used for batch configuration and upgrade of different versions of communication equipment.

When uploading the configuration data, the function of selecting the target communication device is provided, and multiple target communication devices can be selected and uploaded in parallel as required, and batch configuration of multiple target communication devices is performed.

The configuration is performed by downloading the configuration data description file to the local, and the locally configured configuration data description file is uploaded in the way of resuming the breakpoint, so that the offline configuration of the communication device can be realized, the degree of manual intervention is reduced, and the efficiency is improved. Automation of configuration management.

Before the configuration data is actually loaded, the configuration data uploaded to the target communication device is preprocessed according to the actual operating environment of the communication device, which helps to find potential problems, reduces the time required for configuration operations, and improves the accuracy of configuration operations. Consistency and completeness.

The communication device batch configuration management method proposed by the embodiment of the present invention can not only realize the configuration of multiple configuration items for one communication device at the same time, but also realize the configuration of one or more configuration items for multiple communication devices at the same time.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (24)

1, a kind of communication apparatus batch configuration managerial approach is characterized in that, comprises step:

Based on unified descriptor format each configuration data in communication equipment is described;

Download the configuration data of describing based on unified descriptor format in the described communication equipment;

The loading of configuration data parsing is shown to the external world edits;

Configuration data after the external world edited is uploaded to selected target communication device;

Controlling described target communication device loads the configuration data that receives.

2, the method for claim 1 is characterized in that, each configuration data in communication equipment is described based on Interface Microstructure description document, control law description document and three parts of data content description document.

3, method as claimed in claim 2 is characterized in that, described Interface Microstructure description document is used for the tissue of communication device configured project on the interface showed and is described, and specifically is divided into following level Four and describes:

The first order is described product information;

Device type information is described in the second level;

The third level is described device version information;

The fourth stage is described the configuration project information.

4, method as claimed in claim 2, it is characterized in that, described control law description document is used for the correctness of the concrete configuration field of communication equipment and the control of interface element are described, and specifically is divided into to configuration item purpose control description with to the action button of the configuration project support describing.

5, method as claimed in claim 4 is characterized in that, described configuration item purpose control is described specifically is divided into following level Four and describes:

The first order is described the whole control of configuration item purpose;

The form of configuration data is described in the second level;

The third level is described the control of configuration field;

The fourth stage is described the attribute of configuration field own.

6, method as claimed in claim 2 is characterized in that, described data content description document is used for the configuration data value is described, and specifically is divided into following level Four and describes:

The first order is described facility information;

The configuration project is described in the second level;

The third level is described configuration line;

The fourth stage is described configuration field.

7, as the described method of 1～6 arbitrary claim, it is characterized in that, come configuration data in communication equipment is described based on extend markup language.

8, the method for claim 1 is characterized in that, also comprises step:

Configuration data behind the editor carries out verification to external world, and

The verification object information is offered the external world.

9, the method for claim 1 is characterized in that, according to being the selected configuration mode of described target communication device in advance, the corresponding data content uploading that comprises in the configuration data after the external world is edited is given target communication device.

10, method as claimed in claim 9 is characterized in that, described configuration mode is meant: behind the existing configuration data, insert the covering configuration mode of the new configuration data after the external world edits on the deletion target communication device.

11, method as claimed in claim 9 is characterized in that, described configuration mode is meant: the corresponding data content in the configuration data after editing based on the external world, the renewal configuration mode of corresponding legacy data content in the renewal target communication device.

12, the method for claim 1 is characterized in that, if interrupt, continues the configuration data of not uploading next time from interruptions in the configuration data upload procedure.

13, the method for claim 1 is characterized in that, also comprises step:

With the configuration data that uploads on the target communication device, the actual motion environment current according to target communication device carries out preliminary treatment, and

The preliminary treatment object information is offered the external world;

After the preliminary treatment success, the controlled target communication equipment loads the configuration data of preliminary treatment success.

14, a kind of communication apparatus batch configuration management device is characterized in that, comprising:

The configuration data description unit is used for based on unified descriptor format each configuration data in communication equipment being described;

The configuration data download unit is used for downloading the configuration data that described communication equipment is described based on unified descriptor format;

The configuration data resolution unit is used for that the loading of configuration data parsing is shown to the external world and edits;

The configuration data uploading unit, the configuration data after being used for the external world edited is uploaded to selected target communication device;

The data load control unit is used to control described target communication device the configuration data that receives is loaded.

15, device as claimed in claim 14, it is characterized in that described configuration data description unit is described based on Interface Microstructure description document, control law description document and three parts of data content description document each configuration data in communication equipment.

As claim 14 or 15 described devices, it is characterized in that 16, described configuration data description unit comes configuration data in communication equipment is described based on extend markup language.

17, device as claimed in claim 14 is characterized in that, also comprises the configuration data verification unit, and the configuration data after being used for editing to external world carries out verification, and the verification object information is offered the external world.

18, device as claimed in claim 14, it is characterized in that, described configuration data uploading unit is according to being the selected configuration mode of described target communication device in advance, and the corresponding data content uploading that comprises in the configuration data after the external world is edited is given target communication device.

19, device as claimed in claim 14 is characterized in that, described configuration data uploading unit if interrupt, continues the configuration data of not uploading next time from interruptions in the configuration data upload procedure.

20, device as claimed in claim 14, it is characterized in that, also comprise the configuration data pretreatment unit, be used for the configuration data that to upload on the target communication device, the actual motion environment current according to target communication device carries out preliminary treatment, and the preliminary treatment object information is offered the external world;

Data load control unit controlled target communication equipment loads the configuration data of preliminary treatment success after the preliminary treatment success.

21, a kind of communication apparatus batch configuration managerial approach is characterized in that, comprises step:

Configuration data in the download communication equipment;

Based on unified descriptor format loading of configuration data is described;

To be shown to the external world based on the configuration data parsing that unified descriptor format is described edits;

Configuration data after the external world edited is uploaded to selected target communication device;

Controlling described target communication device loads the configuration data that receives.

22, method as claimed in claim 21 is characterized in that, loading of configuration data is described based on Interface Microstructure description document, control law description document and three parts of data content description document.

23, a kind of communication apparatus batch configuration management device is characterized in that, comprising:

The configuration data download unit is used for the configuration data of download communication equipment;

The configuration data description unit is used for based on unified descriptor format loading of configuration data being described;

The configuration data resolution unit, the configuration data parsing that is used for describing based on unified descriptor format is shown to the external world and edits;

The configuration data uploading unit, the configuration data after being used for the external world edited is uploaded to selected target communication device;

The data load control unit is used to control described target communication device the configuration data that receives is loaded.

24, device as claimed in claim 23 is characterized in that, described configuration data description unit is described based on Interface Microstructure description document, control law description document and three parts of data content description document loading of configuration data.

Images