WO2009012696A1

WO2009012696A1 - A communication device batch configuration managing method and the apparatus thereof

Info

Publication number: WO2009012696A1
Application number: PCT/CN2008/071658
Authority: WO
Inventors: Qiuhong Liu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-07-24
Filing date: 2008-07-16
Publication date: 2009-01-29
Also published as: CN100566357C; CN101083684A

Abstract

A communication device batch configuration managing method and the apparatus thereof belong to the communication field. The method includes: describing configuration data in every communication device based on a uniform description format; downloading the configuration data described by the uniform description format in the devices; analyzing and displaying the downloaded configuration data to outside for editing; uploading the configuration data edited by outside to the selected target communication device; controlling the target communication device to load the received configuration data. The apparatus includes a configuration data describing unit, a configuration data downloading unit, a configuration data analyzing unit, a configuration data uploading unit, and a data loading and controlling unit. It can carry out the data configuration accurately, effectively, expandably and off-line by adopting the general communication device batch configuration managing method provided by the invention, avoid the prolixity and error proneness of the hand-collocated manner, and improve the accuracy of the data configuration.

Description

Method and device for batch configuration management of communication equipment

The present invention relates to the field of communications, and in particular, to a method and apparatus for batch configuration management of a communication device. Background technique

Currently, configuring and managing devices is an important means to maintain the normal and orderly operation of communication devices. It initializes devices and configures data for devices to enable devices to provide normal service services or optimize device performance.

For most network maintenance personnel, data configuration and modification of the device is still a manual process. This process is barely capable of maintaining a small number of devices, but for common configuration operations in multiple or entire communication networks. Or a large data volume configuration operation (such as office data creation, book billing data adjustment, batch service loading/unloading, batch overhead, batch card opening, etc.), if the network maintenance personnel separately configure each device Or, by using the configuration command to configure related data one by one (if the number segment is modified, the modification command needs to be executed one by one for each changed number segment), which will result in a large maintenance task and low efficiency. The next step is to solve the problem by batch configuration of communication devices.

The characteristics of batch configuration data should include at least one of the following scenarios:

(1) Configure multiple configuration items simultaneously for one device.

(2) Configure one or more configuration items simultaneously for multiple devices.

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

One is based on a graphical user interface (GUI) to provide visual maintenance of batch data processing functions for network maintenance personnel. On the user interface, some configuration items related to functions on each type of device are classified. When combined, the network maintenance personnel can execute the configuration commands on the interface in sequence to complete the batch data configuration of the device.

However, when using the batch data configuration method for batch configuration data, if the configuration requirements change, you need to rewrite the application according to the changed demand information to get the updated user interface, which will limit the application flexibility of this configuration mode. Sex, that is, the scalability of the configuration function is poor.

At the same time, the batch data configuration mode refers to batch configuration of multiple configuration items that are related to one device at the same time. When faced with data configuration for a large number of devices (for example, in the start, upgrade, and cutover of the communication system) In the middle, routers, access servers, and other ports need to be configured.) Users can only perform each device on the interface. Repeated steps are not only cumbersome, inefficient, but also require many parameters to be manually entered, 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 the text file for the network maintenance personnel. The network maintenance personnel manually modify the relevant data in the text file and then load it into the device by using the import tool, which is generally Load into the device's memory, database, or configuration file.

However, when using this batch data configuration method for batch configuration data, because the configuration file is directly modified, and there is no timely data correctness check, the user must be familiar with the format and context of the configuration file to be correctly modified. For some places with strong data correlation, if the configuration is inconsistent, the whole network will be blocked, and if there is any inconsistency in the network, it must rely on manual inspection. Further, network maintenance personnel must be online to load the configuration file onto the device, and once the load fails, the process must be repeated manually. Summary of the invention

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

The embodiment of the invention provides a method for batch configuration management of a communication device, and the method includes:

Describe the configuration data in each communication device based on the unified description format;

Downloading configuration data in the communication device based on a unified description format description;

Parsing the downloaded configuration data to the outside world for editing;

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 invention further provides an apparatus for batch configuration management of a communication device, the device comprising:

a configuration data description unit (141), configured to describe configuration data in each communication device based on a unified description format;

a configuration data download unit (142), configured to download configuration data in the communication device based on a unified description format description;

The configuration data parsing unit (143) is configured to parse and display the downloaded configuration data to the outside world for editing; the configuration data uploading unit (144) is configured to upload the externally edited configuration data to the selected target communication device; The control unit (145) is configured to control the target communication device to load the received configuration data. The embodiment of the invention further provides a method for batch configuration management of a communication device, the method comprising: downloading configuration data in the communication device;

Describe the downloaded configuration data based on the unified description format;

Parsing and displaying the configuration data based on the unified description format description to the outside world for editing; Uploading the edited configuration data to the selected target communication device;

The embodiment of the present invention further provides a device for managing batch configuration of a communication device, where the device includes: a configuration data download unit (151), configured to download configuration data in the communication device;

The configuration data description unit (152) is configured to describe the downloaded configuration data based on the unified description format; the configuration data parsing unit (153) is configured to parse and display the configuration data based on the unified description format description to the outside world for editing;

The configuration data uploading unit (154) is configured to upload the externally edited configuration data to the selected target communication device; the data loading control unit (155) is configured to control the target communication device to load the received configuration data. . The method for batch configuration management of a communication device according to an embodiment of the present invention is configured to download configuration data on a communication device to a local modification, and then batch configuration to the target communication device. It avoids lengthy and error-prone manual configuration and improves the accuracy of data configuration. DRAWINGS

FIG. 1 is a flowchart of a method for batch configuration management of a communication device according to an embodiment of the present invention;

2 is a block diagram of a configuration data description file according to an embodiment of the present invention;

3 is a block diagram of an interface organization description file according to an embodiment of the present invention;

4 is a block diagram of a content of a control rule description file according to an embodiment of the present invention;

FIG. 5 is a block diagram showing the content of a data content description file according to an embodiment of the present invention; FIG.

FIG. 6 is a schematic diagram of a tree structure on a left side of an analysis interface according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of a structure of a table on the right side of an analysis interface according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of an interface when adding configuration data according to an embodiment of the present invention; FIG.

FIG. 9 is a schematic diagram of an interface of a check result list according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of an interface configuration of a target communication device according to an embodiment of the present invention;

FIG. 11 is a flowchart of configuration data uploading according to an embodiment of the present invention;

FIG. 12 is a flowchart of performing batch configuration management on communication devices of different versions of the same type according to an embodiment of the present invention;

FIG. 13 is a flowchart of configuring data upgrade for a target communication device according to an embodiment of the present invention; FIG.

FIG. 14 is a schematic structural diagram of an apparatus for batch configuration management of a communication device according to an embodiment of the present invention; FIG. 15 is a schematic structural diagram of another apparatus for batch configuration management of a communication device according to an embodiment of the present invention. detailed description

The first technical solution proposed by the embodiment of the present invention is:

Downloading configuration data in the communication device based on the unified description format description, and displaying the downloaded configuration data to the outside world for editing;

The externally edited configuration data is uploaded to the selected target communication device, and the control target communication device loads the received configuration data.

A preferred implementation is to describe the configuration data in Extensible Marker Language (XML), generate a configuration data description file, and parse the configuration item description file downloaded to the local XML description to obtain a common visual configuration. Interface, network maintenance personnel perform editing and configuration operations on the premise of perfect prompting and verification functions on the configuration interface, and then select one or more target communication devices, and upload the locally configured data to the resume transmission method by means of breakpoint transmission. On the target communication device, after the pre-processing is performed according to the current actual running environment of the target communication device, the configuration data is actually loaded onto the target communication device, thereby performing automatic batch configuration on multiple target communication devices.

Specific embodiments of the present invention are described below in conjunction with the drawings.

Referring to FIG. 1, an embodiment of the present invention provides a method for batch configuration management of a communication device, which specifically includes: Step 101: Describe configuration data in each communication device according to a unified description format, that is, adopt a common data description method to configure The data is described, and a configuration data description file is generated.

In a communication device, configuration data is usually stored in the form of a plain text file, an in-memory table or a database, a Management Information Base (MIB), and the like. But regardless of the form, it can be divided into the configuration data content part and the data description part, which is usually called the data dictionary. In the configuration data content part, it is usually stored in the form of a two-dimensional relation table; in the data dictionary part, the storage location of the data corresponding to each configuration item, the data type of the field, the value range constraint, the business logic, and the like are described. If the communication device needs a certain record during the running process, the corresponding data content can be found according to the description of the data dictionary.

In order to generate a common configuration data description file that is easy to edit, view, and process, and to adapt to a communication device that changes frequently in configuration items and often needs to be upgraded, considering the flexibility and scalability of the configuration data description file, the embodiment of the present invention adopts an XML file. To describe.

Since the communication system can be configured in the order of the product one device type and one device version one 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 valued. Scope constraints, data types, business logic, and interface display are described in multiple angles. Therefore, the configuration order, configuration data, and constraints on configuration data can be described to completely describe the configuration data on the communication device. Come. The present invention employs three XML files to describe the 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 following three parts are explained in detail separately:

The interface organization description file 201 is used to describe the organization display of the configuration items of the communication device on the interface, and specifically includes the display order and hierarchical relationship of the configuration items. Each product corresponds to an interface organization description file. Referring to FIG. 3, the interface organization description file 201 is divided into four levels, and the contents in each level are sequentially stored in the order shown 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 The fourth level is the configuration item information 304, including the configuration item ID, the configuration item name, and whether the interface is displayed or the like. In particular, for a virtual configuration item that is on a directory, a specific configuration item can be nested under it. Through the four levels of description, the organization order and hierarchical relationship of all configuration items under one product can be described in the interface; in particular, the public configuration of the corresponding device type can be directly linked under the device type information level of the second level. Projects, these configuration items are common to all versions underneath.

The following is an example of an interface organization description file 201. Where product is the product label and belongs to the product information

301 level; devtype is a device type label, belonging to device type information 302-level; common is a public configuration label, which is hung under device type information 302-level; version is device version label, belonging to device version information 303-level; fun is The configuration item label belongs to configuration item information 304-level. The other symbols used in the XML in the example are: id is the identification attribute corresponding to each level; disp is the display attribute corresponding to each level; name is the name attribute corresponding to the above levels.

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

</common>

<fun id="000184021004" disp="l" name="Portal node configuration"

</fun> </version>

</version>

</devtype>

</product>

As can be seen from the above example, the interface description file 201 can easily describe the interface presentation relationship between configuration items, and it is easy to expand. For example, adding a configuration item can add a fim at the corresponding level. Labels and corresponding attributes; delete a configuration item to delete the corresponding label. By the same token, it is convenient to implement the addition and removal of a device type and device version.

The control rule description file 202 is used to describe the correctness of the specific configuration fields in the communication device and the control of the interface elements, and specifically includes the data correctness control rules and the control rules displayed by the interface. Each configuration item corresponds to a control rule description file.

Referring to Figure 4, the control rule description file 202 includes two parts, one for the configuration item control description 410 and the other for the interface element control description 420.

In the configuration item control description 410 part, it is divided into four levels: The first level is the overall control description 411 of the configuration item, including the configuration item ID, the presence or absence of the index, the ID of the parent configuration item, and whether it is a leaf on the configuration item function tree interface. Node, whether to display, configuration item description, page verification program class and other information; The second level is the table description 412 of the configuration data, mainly the display type of the table on the interface, such as horizontal display according to the field order, vertical display of the field, etc.; The third level is the control description 413 of the configuration field, mainly the interface display control, the data correctness check rule, and the like, including the field ID, the name, the object identifier (OID, Object Identifier), the data type, the value range, and the storage. Whether to read permissions, whether to display on the interface, edit box type (such as text box or drop-down box, etc.), edit box interface display size (in pixels), whether primary key, default value, required or not, prompt information (Tips ), associated with the field ID in the sub-table, the checksum of the button 1", the check rule at the time of submission, the edit box Whether initial activation, whether other columns can be activated, conditions for activating other columns, activated field IDs, types that cannot be repeated (only within a communication device or unique within the entire communication network, etc.), if the value comes from Other configuration rules give the value rule, if it is a string, the formatting rule is given, if the selection box allows multiple selection, whether to ignore the case, whether to allow line breaks, to prohibit the input of the character set, if the field is not a corresponding one The value is a table to give the ID of the configuration table and other information; the fourth level is the attribute description 414 of the configuration field, mainly the enumeration value mapping relationship corresponding to the configuration field, and the automatic generation rule of the configuration field value. The interface element description 420 and the table description 412 of the second-level configuration data in the configuration item control description 410 are juxtaposed at the same level, mainly including the button ID, the button title, the action type of the button, and the button execution completion. The operations that need to be performed, etc. The following is an example of a control rule description file 202:

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

</table>

</buttons>

</fiin>

As can be seen from the above example, it is convenient to describe the interface display, permission control and data legality verification of the configuration item by controlling the rule description file, so that the configuration item can be conveniently parsed into a visual interface. Edit, to ensure the correctness of the data.

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

The following is an example of a data content description file 203:

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

</row> </fun>

</dev>

As can be seen from the above example, the two-dimensional relationship of the configuration data can be conveniently described by the data content description file 203. The configuration item name and the field name in the data content description file 203 are actually redundant information, specifically Excluding the corresponding information in the control rule description file 202, the information is only available in the local data content description file, and the data content description file actually transmitted to the communication device does not include the information. The purpose of this is to facilitate manual viewing or editing without parsing the presentation.

From the three parts included in the configuration data description file 200, the master-slave table in the communication device can be described by the interface organization description file 201, and the actual data is stored separately. For a relational description that a table can be associated with a configuration table by a control rule, the data of the primary table and the secondary table are actually stored separately. This brings great flexibility and scalability to the data description.

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

Step 102: Download the configuration data based on the unified format description in the communication device, and download the configuration data based on the unified format description on the communication device to be configured to the local client, as the basis of the batch configuration data.

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

Step 103: Parsing and displaying the downloaded configuration data. In order to facilitate the user to perform editing and legality verification on the local client, the configuration data is parsed into a visual interface according to some rules defined in the configuration data description file 200, and the visualization is performed. In the interface, the configuration data is displayed in the form of the left tree and the right table. The left tree is hierarchically displayed according to the product one device type, one device version, one device name, and one configuration item. See Figure 6, which is a schematic diagram of the left tree.

A hyperlink is provided at the configuration item level of the left tree, and the configuration item name is clicked, and the display information of each configuration field is obtained from the corresponding control rule description file 202 according to the ID of the current configuration item, and the column headings of the two-dimensional table are organized. Then, the data corresponding to the current configuration item ID is obtained from the data content description file 203, and the data of all the fields is assembled into a two-dimensional table displayed one by one in the upper right according to the line number and the column number.

For an extended table, that is, a case in which a table is nested in a field, the configuration item ID corresponding to the field is first found, and then the corresponding configuration data content is found according to the ID, and finally the assembly of the two-dimensional table is completed line by line. On the interface. For a master-slave table, that is, a row of records corresponding to a two-dimensional table, the main table is displayed in the upper right half, and the table is displayed in In the lower right half, each has its own button operating area. The relationship between the slave table and the master table is expressed by the parent configuration item ID in the control rule description file 202. Each time a record of the master table is selected, the corresponding slave table data is displayed below, as shown in FIG. 7 .

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

Step 104: Edit the configuration data, that is, the user performs the addition, deletion, and modification operations of the configuration data according to related prompts on the interface, so that the input data is desired by the user. Here, there is a complete information entry prompt for the editing process of the configuration data, thereby improving the efficiency of editing the configuration data.

Step 105: Verify the edited configuration data, perform correctness verification such as data validity and service relevance on the editing interface, and ensure the correctness of the configuration data.

The user needs to perform data verification when editing the configuration data for submission. These include: data type check, range constraint check, uniqueness check, data format check, data association, business logic check, and so on. After the verification is completed, the verification result will be displayed on the interface for user confirmation and correction. See Figure 9 for details. The contents of the verification result list here include: configuration item name, field name, field value, error information description, and so on. If the configuration data is incorrect, the user can return to the editing interface according to the error reason and continue to modify until the configuration data is correct.

Step 106: Set the target communication device. Depending on the needs of the batch configuration, one or more communication devices can be selected as the target communication device for configuration.

When the user edits all the configuration data of a communication device, the target communication device to be configured can be selected. The process includes: selecting a source device name of the configured data on the tree of the left configuration item, and displaying the same category and the same version as the source communication device according to the configuration data content description file 200 on the right interface. The current user has a list of target communication devices with the operation authority; the user can also click the device type name on the left configuration item tree, and according to the configuration data content description file 200, the current user has the operation permission under the device type on the right interface. A list of target communication devices is shown in FIG. 10, wherein the user can select one or more target communication devices according to actual configuration requirements.

Step 107: Set the configuration mode of the target communication device. That is, an appropriate mode is selected to perform the configuration operation according to the needs of the target communication device configuration.

Among them, different configuration modes have different effects on the original data on the target communication device. Configuration mode in this embodiment There are two ways to cover configuration and update configuration. The overlay configuration refers to completely inserting new data edited by the user after deleting the configuration data existing on the target communication device. The updating configuration refers to updating the corresponding original data content in the target communication device based on the corresponding content in the edited configuration data of the user, that is, replacing the part of the data on the target communication device that has new configuration data. Operation; No change is made to the part of the data on the target communication device that is not available in the new configuration data; the part of the data that is not in the new configuration data on the target communication device is inserted. In addition, some configuration requirements are either full coverage or update coverage. In this case, this step is optional. In actual operation, according to the actual configuration requirements, the configuration mode can be set for each target communication device, and the configuration mode can be set for all target communication devices in sequence.

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

See Figure 11, for a flow chart for uploading configuration data to a target communication device:

Step 1101: Take the name, IP address, and connection port of the target communication device.

Step 1102: Check whether the running status of the target communication device is normal. If yes, go to step 1103; otherwise, indicate that data configuration is currently unavailable, and repeat step 1102.

Step 1103: Read the breakpoint information at the time of the last upload interrupt as the starting point for uploading the configuration data.

Step 1104: Establish a connection with the target communication device.

Step 1105: Upload configuration data to the target communication device.

Step 1106: If the uploading process is interrupted due to a problem with the target communication device, causing the uploading process to be interrupted, step 1107 is performed; if there is no problem with the target communication device during the uploading process, step 1108 is performed.

Step 1107: Save the breakpoint information of the upload process, and then return to step 1101.

Step 1108: Check whether the configuration data is completely uploaded. If yes, the process of uploading the configuration data ends. Otherwise, return to step 1105.

The process of uploading configuration data enables the embodiment of the present invention to implement off-line configuration of the target communication device, and can automatically detect and automatically upload the video communication device even if the target communication device is disconnected, thereby greatly reducing the degree of manual intervention. Improved automation of configuration management.

Step 109: Pre-processing the configuration data, that is, pre-processing the configuration data uploaded to the target communication device according to the current actual running environment of the target communication device, and providing the pre-processing result information to the user.

The pre-processing includes data consistency check, data conversion, resource application, memory or database, etc., converting the configuration data into an operation command on the running environment of the target communication device, and decomposing the configuration data file into several different configuration files. Convert to the internal required format, etc., in order to ensure the consistency and correctness of the data in the actual environment. Pre-processing is the operation inside the target communication device, which helps to identify potential problems before actually implementing the configuration data, reduce the time required to configure the data, and ensure the success of the configuration operation.

Because the configuration data that is delivered usually involves multiple functional components, its logical structure and association relationship are complex and difficult to locate. If the implementation fails, the complexity of network maintenance will increase. After step 109, the pre-processing report is output to the user for analysis and viewing. The contents of the pre-processing report mainly include: configuration item name, field name, field value, error information description, repair suggestion, etc. If the pre-processing results are all correct, the pre-processing is directly prompted to be successful. Otherwise, the pre-processing report is downloaded to the user for viewing. The user may re-download the configuration data description file of the target communication device according to the error reason and the repair suggestion, and edit or directly return to the editing. The interface continues to be modified until the configuration is correct. In particular, in some configuration scenarios where the configuration data does not involve a memory allocation, a resource application, or a database update, the foregoing pre-processing operations may not be required. In this case, this step is optional.

Step 110: Load the configuration data, that is, after the pre-processing succeeds, the control target communication device loads the configuration data for the pre-processing success, thereby completing the data configuration operation.

The configuration data is split into a configuration file corresponding to different functional components inside the target communication device, and formatted into an internal required format; thereby completing, adding, deleting, and modifying data to the managed object inside the target communication device, and Convert configuration data to actual run commands, and more. After the configuration data is loaded, the target communication device can operate according to the new configuration state.

The process of data configuration using the present invention in two common cases of communication device configuration is given below.

1. Configure batch data of different versions of the same communication device type to adapt to the phenomenon and requirements of coexistence of different versions of the existing communication devices. For example, in a communication system, there are two versions of the infoX AAA device, one low version and one high version, both of which have most of the same configuration items. It is not necessary to configure the configuration items for each version from start to finish. The specific process is shown in Figure 12:

Step 1201: Unifiedly editing and verifying common version data of different versions;

Step 1202: Perform editing and verification of respective configuration data of different versions respectively.

Step 1203: Set different types of communication devices of the same type as target communication devices;

Step 1204: Set a configuration mode of the corresponding version target communication device;

Step 1205—Step 1207: Performs batch uploading, pre-processing, and loading of the configuration data, which is similar to the steps 108-110, and is not described here. At this time, all configuration items of communication devices of different versions of the same communication device are configured.

Second, the upgrade of the communication device configuration data to adapt to the ever-changing needs of the communication device configuration data. For example, in a communication system, the infoX AAA device is upgraded from a lower version to a higher version. For the specific process, refer to FIG. 13: Step 1301: Initialize a parameter type that represents a higher version relative to a lower version change type, and assign type=0. When type=0, it indicates that there is no version upgrade; Step 1302: comparing the high version with the lower version, determining whether the lower version of the configuration item or field is deleted, if yes, executing step 1303; otherwise, executing step 1304;

Step 1303: If the high version is deleted compared with the lower version, the data that exists in the low version configuration content and is not needed by the high version is deleted and converted into a high version content file. Set type=l, and then proceed to step 1304; Step 1304: Determine whether the high version has several new configuration items or whether there are newly added fields or new data records in the original configuration item. If yes, go to step 1305; otherwise, if the high version does not increase compared with the low version, go directly to step 1306;

Step 1305: If the high version is compared with the lower version, the configuration data of the lower version is not according to the high-level interface organization file and the control rule description file, but the configuration data in the new version is first used with null data or missing. After the value is filled, the configuration data is converted to a higher version, that is, the new configuration data is configured according to the configuration rule of the high version, and type=2 is set _; then, step 1306 is continued;

Step 1306: If there is a configuration item in the high and low version, it is determined whether the field control range, the data type, and the like in the configuration item in the high version have changed compared with the low version. If yes, step 1307 is performed; Bay U, directly perform step 1308;

Step 1307: If the validity control rule such as the field range or the data type in the same configuration item of the high version and the lower version changes, directly modify the lower version of the data content file, and change the changed data according to the constraint of the new version. The rules are modified to meet the description of the high-level interface organization and control rules; set type=3, and then continue to step 1308;

Step 1308: Determine whether there is a version upgrade, that is, determine whether type is equal to 0, and if so, the configuration data upgrade process ends; otherwise, step 1309 is performed;

Step 1309: Determine whether the type type is only a high version and a relatively low version, that is, whether the type is equal to 1, if not, proceed to step 1310; if yes, perform step 1311;

Step 1310: Parsing the data content file after modifying the low-level configuration data content file according to the high-level configuration rule, and converting to a visual interface for editing and verifying the configuration item, wherein the processes of parsing, editing, and verifying are respectively referred to Step 103, step 104 and step 105, which are not described in detail herein;

Step 1311: Set the corresponding target communication device and configuration mode, upload the configuration data file, perform pre-processing of the data file, and perform actual loading of the configuration data after the pre-processing is successful, so that the updated target communication device runs under the new version. The pre-processing operation of setting the configuration mode and the data file is optional. For details, refer to Step 107 and Step 109, and details are not described here.

The method for batch configuration management of a communication device according to the embodiment of the present invention uses XML to describe configuration data, and generates a general configuration data description file that is easy to edit, view, and process, and can be conveniently parsed by using the file. Visualized user interface, network maintenance personnel have a comprehensive prompt function and data verification function when performing configuration editing on the visual interface, which ensures the accuracy of data configuration. In addition, due to the flexibility and scalability of the configuration file, it is possible to adapt to communication devices where the configuration items change frequently and often need to be upgraded;

When uploading configuration data, the selection function of the target communication device is provided, and multiple target communication devices can be selected to be uploaded in parallel according to requirements, and multiple target communication devices are batch-configured;

Further, the configuration data file is downloaded to the local device for configuration, and the locally configured configuration data description file is uploaded by using a breakpoint resume transmission, thereby enabling off-line configuration of the communication device and reducing the degree of manual intervention. , improve the automation of configuration management;

Before the configuration data is actually loaded, pre-processing the configuration data uploaded to the target communication device according to the actual running environment of the target communication device helps to identify potential problems, reduces the time required for configuration operations, and improves the accuracy of the configuration operation. Sex, consistency and integrity;

In addition, the method for managing batch configuration of a communication device according to the embodiment of the present invention can not only implement configuration of multiple configuration items for one communication device at the same time, but also enable configuration of one or more configuration items for multiple communication devices simultaneously. . According to the technical solution of the foregoing method embodiment, the embodiment of the present invention further provides a device for managing batch configuration management of a communication device, and the device for configuring batch management of the communication device includes:

The configuration data description unit 141 is configured to describe configuration data in each communication device based on the unified description format, and the description may be, but is not limited to, three parts based on an interface organization file, a control rule file, and a data content description file. A preferred implementation is to use a generic XML language to describe configuration data in a communication device.

Configuration Data Download Unit 142: Used to download configuration data based on a unified description format description in the communication device. The configuration data parsing unit 143 is configured to parse and display the downloaded configuration data to the outside world for editing.

The configuration data uploading unit 144: is used to upload the externally edited configuration data to the selected target communication device. When uploading, the corresponding data content included in the externally edited configuration data may be uploaded to the target communication device according to the configuration mode selected in advance for the target communication device. A preferred implementation method is to interrupt the configuration data upload process, and continue to upload the un-uploaded configuration data from the interruption.

The data loading control unit 145 is configured to control the target communication device to load the received configuration data.

Further, the above apparatus may further include:

The configuration data verification unit 146 is configured to perform verification on the externally edited configuration data, and provide the verification result information to the outside world. Further, the above apparatus may further include:

The configuration data pre-processing unit 147: is configured to pre-process the configuration data uploaded to the target communication device according to the current actual operating environment of the target communication device, and provide the pre-processing result information to the outside world.

Correspondingly, the data loading control unit 145 is specifically configured to control the target communication device to load the configuration data of the pre-processing success after the pre-processing is successful.

The configuration data verification unit 146 and the configuration data preprocessing unit 147 in the apparatus for batch configuration management of the communication device are optional. In addition, the various functional units mentioned in the above apparatus may be implemented based on software programming, or may be implemented based on retrofitting existing hardware devices.

In the embodiment of the present invention, the configuration of the communication device is improved by directly transmitting the configuration data file to the target communication device, instead of issuing the configuration command one by one. It can therefore be used for batch configuration and upgrade of different versions of communication devices. The technical solution of the foregoing method embodiment is applicable to the configuration data in each managed communication device in the communication system has been described based on a unified description format. However, in the actual network system, there may be some original communication devices. The configuration data in the configuration is not upgraded, that is, the configuration data in some original communication devices is not described using a unified description format, and in order to achieve the object of the present invention, the present embodiment further provides another communication device. The method of batch configuration management includes:

Download configuration data in the communication device;

Parsing and displaying the configuration data based on the unified description format description to the outside world for editing;

The control target communication device loads the received configuration data.

The downloaded configuration data is described based on three parts: an interface organization description file, a control rule description file, and a data content description file. For details about other technical implementations, please refer to the related description of the first method embodiment, and details are not described herein again.

In the embodiment of the present invention, the configuration data on the communication device is downloaded to the local modification, and then batch configured to the target communication device, thereby improving the accuracy of data configuration. Referring to FIG. 15, which is a technical solution corresponding to the foregoing second method embodiment, an embodiment of the present invention provides a device for managing batch configuration of a communication device, which specifically includes:

The configuration data download unit 151: is for downloading configuration data in the communication device. The configuration data description unit 152 is configured to describe the configuration data downloaded by the configuration data download unit 151 based on the unified description format, and the description may be performed by using, but not limited to, three parts: an interface organization file, a control rule file, and a data content description file. description. A preferred implementation is to use a generic XML language to describe configuration data in a communication device.

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

The configuration data uploading unit 154: is configured to upload the externally edited configuration data to the selected target communication device. The data loading control unit 155: is configured to control the target communication device to load the received configuration data.

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

The embodiment of the present invention improves the efficiency of configuration of the communication device by directly transmitting the configuration data file between the device for managing the batch configuration of the communication device and the target communication device instead of issuing the configuration command one by one.

The embodiments of the present invention can be implemented by software, and correspondingly, the software can be stored in a readable storage medium, such as a hard disk, a floppy disk or an optical disk of a computer.

It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and the modifications of the invention

Claims

Claim

A method for batch configuration management of a communication device, the method comprising:

Parsing the downloaded configuration data to the outside world for editing;

2. The method according to claim 1, wherein the describing the configuration data in each communication device is specifically:

The configuration data in each communication device is described based on three parts: an interface organization description file, a control rule description file, and a data content description file.

The method according to claim 2, wherein the interface organization description file is used to describe the organization display of the configuration item of the communication device on the interface, and is specifically described in the following four levels:

The first level describes the product information;

The second level describes device type information;

The third level describes device version information;

The fourth level describes the configuration item information.

The method according to claim 2, wherein the control rule description file is specifically divided into a configuration item control description and an interface element control description.

The method according to claim 4, wherein the configuration item control description is specifically divided into the following four levels: The first level is an overall control description of the configuration item;

The second level is a table description of the configuration data;

The third level is the control description of the configuration field;

The fourth level is the attribute description of the configuration field.

The method according to claim 2, wherein the data content description file is used to describe the configuration data value, and is specifically divided into the following four levels:

The first level is a description of the device information;

The second level is the configuration item description;

The third level is the configuration line description; The fourth level is the configuration field description.

7. The method according to any one of claims 1 to 6, wherein the describing the configuration data in each communication device is specifically:

The configuration data in each communication device is described based on an extensible markup language.

8. The method of claim 1, wherein the method further comprises:

Verify the edited configuration data from the outside world, and

The verification result information is provided to the outside world.

The method according to claim 1, wherein the uploading the externally edited configuration data to the selected target communication device comprises:

The corresponding data content included in the externally edited configuration data is uploaded to the target communication device according to a configuration mode selected in advance for the target communication device.

The method according to claim 9, wherein the configuration mode is: after deleting the configuration data existing on the target communication device, inserting an overlay configuration mode of the externally edited configuration data.

The method according to claim 9, wherein the configuration mode is: updating an update configuration of the corresponding original data content in the target communication device based on the corresponding data content in the externally edited configuration data. mode.

12. The method according to claim 1, wherein if an interruption occurs during the configuration data uploading process, the unuploaded configuration data is continuously uploaded from the interruption.

The method according to claim 1, wherein the uploading the externally edited configuration data to the selected target communication device further comprises:

Pre-processing the configuration data uploaded to the target communication device according to the current actual operating environment of the target communication device, and providing the pre-processing result information to the outside;

Correspondingly, the controlling the target communication device to load the received configuration data is specifically:

After the pre-processing is successful, the target communication device is controlled to load the configuration data of the pre-processing success.

14. A device for batch configuration management of a communication device, the device comprising:

a configuration data description unit (141) for describing configuration data in each communication device based on a unified description format; a configuration data download unit (142) for downloading configuration data based on a unified description format description in the communication device;

The configuration data parsing unit (143) is configured to parse and display the downloaded configuration data to the outside world for editing; the configuration data uploading unit (144) is configured to upload the externally edited configuration data to the selected target communication device; The control unit (145) is configured to control the target communication device to load the received configuration data.

The device according to claim 14, wherein the configuration data description unit (141) pairs each The configuration data in the letter device is described based on three parts: an interface organization description file, a control rule description file, and a data content description file.

The apparatus according to claim 14 or 15, wherein the configuration data description unit (141) describes configuration data in the communication device based on an extensible markup language.

The device of claim 14, wherein the device further comprises:

The configuration data verification unit (146) is configured to perform verification on the externally edited configuration data and provide the verification result information to the outside world.

The device according to claim 14, wherein the configuration data uploading unit (144) is specifically configured to: perform corresponding to the externally edited configuration data according to a configuration mode selected in advance for the target communication device. The data content is uploaded to the target communication device.

The device according to claim 14, wherein the configuration data uploading unit (144) continues to upload the unuploaded configuration data from the interruption if an interruption occurs during the configuration data uploading process.

The device of claim 14, wherein the device further comprises:

a configuration data pre-processing unit (147), configured to pre-process configuration data uploaded to the target communication device according to a current actual operating environment of the target communication device, and provide pre-processing result information to the outside; The data loading control unit (145) is specifically configured to control the target communication device to load the configuration data of the pre-processing success after the pre-processing is successful.

Download configuration data in the communication device;

The method according to claim 21, wherein the describing the downloaded configuration data is specifically: the downloaded configuration data is based on three parts: an interface organization description file, a control rule description file, and a data content description file. To describe.

A device for managing batch configuration of a communication device, the device comprising:

a configuration data download unit (151) for downloading configuration data in the communication device;

The configuration data description unit (152) is configured to describe the downloaded configuration data based on the unified description format; the configuration data parsing unit (153) is configured to parse and display the configuration data based on the unified description format description to the outside for editing; The configuration data uploading unit (154) is configured to upload the externally edited configuration data to the selected target communication device; the data loading control unit (155) is configured to control the target communication device to load the received configuration data. .

The device according to claim 23, wherein the configuration data description unit (152) is specifically configured to: based on the unified description format, the downloaded configuration data is based on an interface organization description file, a control rule description file, and data content. Describe the three parts of the document for description.