WO2016201988A1 - 配置数据推送方法及装置 - Google Patents

配置数据推送方法及装置 Download PDF

Info

Publication number
WO2016201988A1
WO2016201988A1 PCT/CN2016/072487 CN2016072487W WO2016201988A1 WO 2016201988 A1 WO2016201988 A1 WO 2016201988A1 CN 2016072487 W CN2016072487 W CN 2016072487W WO 2016201988 A1 WO2016201988 A1 WO 2016201988A1
Authority
WO
WIPO (PCT)
Prior art keywords
network interface
interface information
network
network element
information
Prior art date
Application number
PCT/CN2016/072487
Other languages
English (en)
French (fr)
Inventor
石国强
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016201988A1 publication Critical patent/WO2016201988A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks

Definitions

  • This application relates to, but is not limited to, the field of communication technology.
  • NETCONF network configuration protocol
  • SNMP Simple Network Management Protocol
  • NETCONF basically solves the shortcomings of SNMP and is suitable for large and complex network management.
  • YANG language is an abstract description language. YANG language is powerful, readable, complete, and extensible. It is the most suitable data modeling language for NETCONF.
  • the network element often has multiple branches, and under the same branch, there are also new and old versions of the network element. There are often differences between network elements of different branches and new and old versions of a branch.
  • the NMS needs to generate the specified configuration data for the difference between the NEs and the NETCONF interface configuration packets are sent to each NE. The interaction causes the configuration data to be pushed less efficiently.
  • This document provides a configuration data push method and configuration to improve the efficiency of configuration data push.
  • a configuration data pushing method where the configuration data pushing method includes:
  • the generating the reference network interface information according to the obtained network interface information of each to-be-configured network element includes:
  • the acquired network interface information of each to-be-configured network element is merged into the reference network interface information according to the obtained keyword and/or the extended keyword in the network interface information of each to-be-configured network element.
  • the network interface information of each of the to-be-configured network elements and the first network interface configuration packet are matched for each network element to be configured and sent a corresponding second network interface configuration packet.
  • the first network interface configuration packet is tailored according to the obtained keyword and/or the extended keyword in the network interface information of each to-be-configured network element, and the tailored first network interface configuration packet is used as the first Two network interface configuration messages;
  • the second network interface configuration packet is sent to each corresponding network element to be configured.
  • the generating the reference network interface information according to the obtained network interface information of each to-be-configured network element includes:
  • the reference network interface information is generated according to the obtained network interface information of each to-be-configured network element.
  • the configuration data pushing method further includes:
  • the corresponding network interface information is modified.
  • a configuration data pushing device comprising:
  • the reference information generating module is configured to: obtain network interface information of each network element to be configured, and generate reference network interface information according to the obtained network interface information of each to-be-configured network element;
  • the configuration packet generating module is configured to: generate a first network interface configuration packet carrying the configuration data according to the reference network interface information;
  • Configuring a message delivery module configured to: match each network element to be configured and send a corresponding second network according to the network interface information of each network element to be configured and the first network interface configuration message Interface configuration packet.
  • the reference information generating module is configured to: obtain the network interface of each to-be-configured network element according to keywords and/or extended keywords in the obtained network interface information of each network element to be configured. The information is merged into reference network interface information.
  • the configuration packet sending module includes:
  • the packet cutting unit is configured to: tailor the first network interface configuration packet according to the obtained keyword and/or the extended keyword in the network interface information of each to-be-configured network element, and the cropped The first network interface configuration packet is configured as the second network interface configuration packet;
  • Configure the packet sending unit to be configured to send the second network interface configuration packet to each corresponding NE to be configured.
  • the reference information generating module is configured to perform a compatibility check on the obtained network interface information of each to-be-configured network element; and, when there is no conflicting item, according to each acquired network element to be configured
  • the network interface information generates reference network interface information.
  • the configuration data pushing device further includes a modifying module, configured to: modify the corresponding network interface information when there is a conflicting item.
  • a computer readable storage medium storing computer executable instructions for performing the method of any of the above.
  • the embodiment of the present invention obtains network interface information of each network element to be configured, and generates reference network interface information according to the acquired network interface information of each network element to be configured; and generates configuration data carrying the configuration data according to the reference network interface information.
  • the first network interface configuration packet is configured to match and send the corresponding second network interface configuration for each to-be-configured network element according to the network interface information of each of the to-be-configured network elements and the first network interface configuration packet Message.
  • the module of each component version of the network element is statically merged as the basis for the configuration data sent by the network management system, and the packet is configured on the carrier NETCONF interface of the configuration data by using the network interface information of the corresponding module. Dynamically adjust the NETCONF interface configuration packet matching the NE branch. The number of interactions between the network management system and the network element is reduced, thereby improving the efficiency of configuration data push.
  • FIG. 1 is a schematic flowchart of a first embodiment of a configuration data pushing method according to the present invention
  • FIG. 2 is a schematic diagram showing a refinement flow of generating reference network interface information in FIG. 1;
  • FIG. 3 is a schematic diagram of functional modules of a first embodiment of a configuration data pushing apparatus according to the present invention.
  • the embodiment of the present invention provides a configuration data pushing method.
  • the configuration data pushing method includes:
  • S10 Obtain network interface information of each network element to be configured, and generate reference network interface information according to the obtained network interface information of each to-be-configured network element.
  • a network element is a network device that forms a network, including servers, clients, routers, and switches.
  • a network element often includes multiple components, each component has a different version, and different versions of the component include multiple modules, and each of the modules in the version has an independent evolution mechanism.
  • the NETCONF interface is used for a functional description module that conforms to the YANG model specification.
  • the YANG (RFC6020) language specifies the structure of a module: it mainly includes header information, link information, meta information, revision information, and module body information.
  • the header information defines the identifier of the module
  • the module body information includes the structure defined by the module and/or other modules (typedef, extension, feature, etc.), and the custom structure of the module (container, choice, case, list, and Leaf, etc.), the custom structure specifies the management scope information of the module.
  • the network running NETCONF The following is a description of the network running NETCONF.
  • Any network element can be configured to send a configuration request to the network management system (the network element is used to control the running of the network element to be configured) to be the network element to be configured.
  • the network management device will mark the NE corresponding to the configuration request as the NE to be configured as long as it receives the configuration request.
  • the device sends Hello packets to the NMS periodically.
  • the Hello packet is an XML message conforming to the NETCONF protocol specification, and is used to maintain the management relationship between the network element to be configured and the network management system, and carries the NETCONF interface information of the network element to be configured, and the component information is advertised in the NETCONF interface information;
  • the component information of the Hello packet is compared with the component information of the component database in the locally stored component database.
  • the NMS recognizes that the NE is in the management scope.
  • the NMS identifies the network. The element is not in the management scope, disconnects from the network element, and refuses to manage.
  • the network management device On the network consisting of the network management system and the network element to be configured, after receiving the Hello message sent by each network element to be configured, the network management device analyzes each Hello message received by the network management device to obtain the NETCONF of each network element to be configured. Interface information (network interface information), the NETCONF interface information describes each module corresponding to the network element to be configured.
  • the communication between the network management system and the network element to be configured is implemented based on RPC (Remote Procedure Call).
  • the NMS runs the NETCONF client.
  • the NE to be configured runs the NETCONF server.
  • the network management system After obtaining the NETCONF interface information of each network element to be configured, the network management system generates the reference NETCONF interface information (reference network interface information) according to the obtained NETCONF interface information of each to-be-configured network element.
  • each NETCONF is The interfaces are merged into one large and full NETCONF interface.
  • the generating the reference network interface information according to the acquired network interface information of each to-be-configured network element includes:
  • the NETCONF interface information of each to-be-configured network element is merged into the reference NETCONF interface information according to the keywords and/or extended keywords in the NETCONF interface information of each to-be-configured network element.
  • the merging refers to combining the meanings of keywords and/or extended keywords in the NETCONF interface information, and semantically analyzing and merging the module body information parts of the same module of multiple versions according to the guiding principle (including node merging and node constraints). Merger).
  • a module of a version component as a reference module (for example, the corresponding module of the network element to be configured that is the first access network management system), and sequentially acquiring the module information of other version components in the order of accessing the network management, and traversing through the preamble
  • the method searches for the same node in the NETCONF interface information corresponding to the reference module. If not, adds the relevant node to the NETCONF interface information corresponding to the reference module.
  • the merge algorithm of this embodiment is as follows:
  • Parent_path getAbsolutePath(module.parent)
  • the merged reference NETCONF interface information will be added with an ncd:device-availabledate extended keyword to mark the module body custom node range.
  • ncd:device-availabledate extended keyword to mark the module body custom node range.
  • the base NETCONF interface information will use two ncd:device-availabledate clauses to indicate the range supported by the node, as follows:
  • the reference NETCONF interface information contains the node, and the ncd:device-availabledate clause is used to indicate that the node is only supported in ZXROSNG V3.00.31, as shown below:
  • a reference NETCONF interface configuration message (a first network interface configuration message) is generated according to the reference NETCONF interface information, and the generated reference NETCONF interface configuration message is an XML message conforming to the NETCONF protocol specification.
  • the document carries the configuration data, and is used to configure the corresponding NETCONF interface of the NE to be configured.
  • the generation process of the reference NETCONF interface configuration packet is implemented according to the NETCONF protocol standard, and is not described here.
  • the reference NETCONF interface configuration message generated based on the above reference NETCONF interface information is as follows:
  • the reference NETCONF interface configuration packet includes configuration data of the track-group-name node and the up-delay node.
  • the network element to be configured is matched and sent according to the NETCONF interface information of the to-be-configured network element and the reference NETCONF interface configuration packet.
  • NETCONF interface configuration message (second network interface configuration message). And extracting part of the data from the reference NETCONF interface configuration packet as the NETCONF interface configuration packet according to the NETCONF interface information of each to-be-configured network element; or cutting out the useless part in the reference NETCONF interface configuration packet, The cut reference NETCONF interface configuration packet is configured as the NETCONF interface configuration packet.
  • the reference NETCONF interface configuration packet is tailored according to the obtained keyword and/or the extended keyword in the NETCONF interface information of each to-be-configured network element, and the cropped
  • the reference NETCONF interface configuration packet is configured as a NETCONF interface configuration packet corresponding to each network element to be configured;
  • the cutting is performed by comparing the reference NETCONF interface configuration packet with the function set of the NETCONF interface information of each to-be-configured network element, and deleting the unsupported function set for the network element to be configured, and dynamically cutting out the matching Configure the NETCONF interface configuration packet of the NE version module.
  • the node range in the reference NETCONF interface configuration packet generated according to the reference NETCONF interface information is compared with the range of the node in the NETCONF interface information of the to-be-configured network element, if the reference NETCONF interface
  • the node component information in the configuration packet (the foregoing ncd extended key field) has a component version of the to-be-configured network element, and the revision date of the corresponding module is not earlier than the enabled timestamp, and the reference NETCONF interface configuration packet is retained.
  • the corresponding node in the middle otherwise delete the corresponding node, optionally, the clipping algorithm used in this embodiment As follows:
  • the track-group-name node exists in the component ZXROSNG V3.00.31 and the component ZXROSNG V2.00.32.
  • the reference NETCONF interface configuration packet does not need to be tailored and can be directly sent.
  • the up-delay node only exists in the In the component ZXROSNG V3.00.31, when the NETCONF interface configuration packet is delivered to the NE that contains the component ZXROSNG V2.00.32, the reference NETCONF interface configuration packet needs to be trimmed, and the up-delay node that is not supported by the component ZXROSNG V2.00.32 is deleted.
  • the cropped NETCONF interface configuration message is as follows:
  • the configuration data pushing method of the present embodiment obtains network interface information of each network element to be configured, and generates reference network interface information according to the acquired network interface information of each network element to be configured; and generates data according to the reference network interface information.
  • the first network interface configuration packet carrying the configuration data; the network interface information of each to-be-configured network element and the first network interface configuration packet are matched and sent for each network element to be configured.
  • the second network interface configures the packet.
  • the module of each component version of the network element is statically merged as the basis for the configuration data sent by the network management system, and the packet is configured on the carrier NETCONF interface of the configuration data by using the network interface information of the corresponding module.
  • the dynamic adjustment is performed, and the NETCONF interface configuration packet conforming to the network element branch is correctly delivered, which reduces the number of interactions between the network management system and the network element, so that the embodiment of the present invention can improve the efficiency of configuration data push.
  • the NE to be configured parses the configuration data carried by the NETCONF interface configuration packet and responds. For example, after the network element to be configured that includes the component ZXROSNG V2.00.32 receives the NETCONF interface configuration packet sent by the network management system, the configuration data is parsed: ⁇ track-group-name>test ⁇ /track-group-name> and ⁇ Up-delay>0 ⁇ /up-delay>, because the aforementioned configuration data is for the zxr10-samgr module included, the value of the zxr10-samgr module track-group-name node is set to test, and the value of the up-delay node is Set to 0.
  • the NETCONF response packet is generated based on the result of the configuration (successful or not), and the NETCONF response packet is returned to the NMS.
  • the NMS After receiving the NETCONF packet returned by the NE to be configured, the NMS receives the NETCONF packet. , the corresponding processing. The processing performed is implemented with reference to the NETCONF protocol standard, and is not described here.
  • the step S10 generates a reference network interface according to the acquired network interface information of each network element to be configured.
  • Information includes:
  • the compatibility check of the acquired NETCONF interface information of each to-be-configured network element is performed before the reference NETCONF interface information is merged.
  • the module of the version component is selected as the reference module (for example, the corresponding module of the network element to be configured that is the first access network management system), and the module information of the other version components is acquired in sequence (accessing the network management system) (NETCONF interface information)
  • NETCONF interface information accessing the network management system
  • the same node is searched for in the NETCONF interface information corresponding to the reference module by the pre-order traversal. If the same node exists, the compatibility check is performed, and the conflict information is recorded.
  • the check items of the compatibility check are as shown in Table 1:
  • module, namespace, prefix, belongs-to statement parameters can not be modified 2.
  • the basic type of the type clause of the same node (including typedef) cannot be modified. 3, the same node config meaning can not be modified 4, the same leaf node display definition units clause parameters can not be modified 5, the key clause of the list statement can not be added or the parameters change (including the order) 6, the unique clause of the list statement can not be added or the parameters can not be changed (including the order) 7, the value defined in the enum clause of the type enumeration can not conflict, the enumeration name can not be modified 8, the position defined by the bit in the type bits can not conflict, the name can not be modified 9, the path clause parameter of the type leafref can not be modified 10.
  • the base clause parameter of type identityref cannot be modified.
  • the configuration data pushing method further includes:
  • the corresponding network interface information is modified.
  • the NETCONF interface information with the conflicting item is modified.
  • the NETCONF interface information with conflicting items is modified according to the constraint rule shown in Table 1, and the conflicting items are eliminated.
  • the NETCONF interface information is merged.
  • the embodiment of the present invention further provides a configuration data pushing device.
  • the configuration data pushing device includes:
  • the reference information generating module 10 is configured to: obtain network interface information of each network element to be configured, and generate reference network interface information according to the acquired network interface information of each network element to be configured;
  • a network element is a network device that forms a network, including servers, clients, routers, and switches.
  • a network element often includes multiple components, each component has a different version, and different versions of the component include multiple modules, and each of the modules in the version has an independent evolution mechanism.
  • the NETCONF interface is used for a functional description module that conforms to the YANG model specification.
  • the YANG (RFC6020) language specifies the structure of a module: it mainly includes header information, link information, meta information, revision information, and module body information.
  • the header information defines the identifier of the module
  • the module body information includes the structure defined by the module and/or other modules (typedef, extension, feature, etc.), and the custom structure of the module (container, choice, case, list, and Leaf, etc.), the custom structure specifies the management scope information of the module.
  • the network running NETCONF The following is a description of the network running NETCONF.
  • Any network element can be configured to send a configuration request to the network management system (the network element is used to control the running of the network element to be configured) to be the network element to be configured.
  • the network management device will mark the NE corresponding to the configuration request as the NE to be configured as long as it receives the configuration request.
  • the network element sends a Hello message to the network management system.
  • the Hello message is an XML message conforming to the NETCONF protocol. It is used to maintain the management relationship between the NE and the NMS.
  • the NETCONF interface information of the network element to be configured is carried out, and the component information is advertised in the NETCONF interface information.
  • the NMS After receiving the Hello message from each network element to be configured, the NMS updates the component information of the Hello message with the locally stored component database.
  • the network management system identifies the network element in the management scope; when the network element to be configured is Hello
  • the network management system identifies that the network element is not in the management scope, disconnects the network element, and refuses to manage.
  • the configuration data pushing device provided in this embodiment is built in the network management system, and the reference information generating module 10 receives the Hello message sent by each network element to be configured after the network management system receives the Hello message.
  • the NETCONF interface information (network interface information) of each network element to be configured is obtained by parsing each Hello packet received by the network management unit, and the NETCONF interface information describes each module corresponding to the network element to be configured.
  • the communication between the network management system and the network element to be configured is implemented based on RPC (Remote Procedure Call).
  • Network management running NETCONF On the client, the NE to be configured runs the NETCONF server.
  • the reference information generating module 10 After obtaining the NETCONF interface information of each to-be-configured network element, the reference information generating module 10 generates a reference NETCONF interface information (reference network interface information) according to the obtained NETCONF interface information of each to-be-configured network element, which is generally said to be Combine each NETCONF interface into a large and full NETCONF interface.
  • the reference information generating module 10 is configured to: obtain the NETCONF interface information of each to-be-configured network element according to the keywords and/or extended keywords in the NETCONF interface information of each to-be-configured network element. Merged into the base NETCONF interface information.
  • the merging refers to combining the meanings of keywords and/or extended keywords in the NETCONF interface information, and semantically analyzing and merging the module body information parts of the same module of multiple versions according to the guiding principle (including node merging and node constraints). Merger).
  • the reference information generating module 10 selects a module of a version component as a reference module (for example, a corresponding module of the first network element to be configured that accesses the network management system), and sequentially acquires the module information of the other version components in the order of accessing the network management system.
  • the preamble traversal method searches for the same node in the NETCONF interface information corresponding to the reference module. If not, the related node is added to the NETCONF interface information corresponding to the reference module.
  • the merge algorithm of this embodiment is as follows:
  • Parent_path getAbsolutePath(module.parent)
  • the reference NETCONF interface information obtained by the reference information generating module 10 will be added with an ncd:device-availabledate extended keyword to mark the module body custom node range.
  • ncd:device-availabledate extended keyword to mark the module body custom node range.
  • the base NETCONF interface information will use two ncd:device-availabledate clauses to indicate the range supported by the node, as follows:
  • the reference NETCONF interface information contains the node, and the ncd:device-availabledate clause is used to indicate that the node is only supported in ZXROSNG V3.00.31, as shown below:
  • the configuration packet generating module 20 is configured to: generate, according to the reference network interface information, a first network interface configuration packet carrying configuration data;
  • the configuration packet generation module 20 generates a reference NETCONF interface configuration packet (the first network interface configuration packet) according to the NETCONF interface standard according to the NETCONF protocol standard, and the generated reference NETCONF interface configuration packet is matched.
  • the XML packet of the NETCONF protocol carries configuration data, which is used to configure the corresponding NETCONF interface of the NE to be configured.
  • the generation process of the reference NETCONF interface configuration packet is implemented according to the NETCONF protocol standard, and is not described here.
  • the reference NETCONF interface configuration message generated based on the above reference NETCONF interface information is as follows:
  • the reference NETCONF interface configuration packet includes configuration data of the track-group-name node and the up-delay node.
  • the packet sending module 30 is configured to: match each network element to be configured and send a corresponding second according to the network interface information of the network element to be configured and the first network interface configuration packet. Network interface configuration packet.
  • the configuration packet delivery module 30 configures the NETCONF interface information of each of the to-be-configured network elements and the reference NETCONF interface configuration report. For each network element to be configured to match and send the corresponding NETCONF interface configuration message (second network interface configuration message).
  • the configuration packet delivery module 30 may extract part of the data from the reference NETCONF interface configuration packet as the NETCONF interface configuration packet based on the NETCONF interface information of each to-be-configured network element, or cut the reference NETCONF interface. Configure the useless part of the packet as the NETCONF interface configuration packet.
  • the configuration packet sending module 30 includes:
  • the packet cutting unit is configured to: cut the reference NETCONF interface configuration packet according to the obtained keyword and/or the extended keyword in the NETCONF interface information of each to-be-configured network element, and cut the benchmark after cutting
  • the NETCONF interface configuration packet is configured as a NETCONF interface configuration packet corresponding to each network element to be configured.
  • the cutting is performed by comparing the reference NETCONF interface configuration packet with the function set of the NETCONF interface information of each to-be-configured network element, and deleting the unsupported function set for the network element to be configured, and dynamically cutting out the matching Configure the NETCONF interface configuration packet of the NE version module.
  • the configuration packet cutting unit compares the node range in the reference NETCONF interface configuration packet generated by the reference NETCONF interface information with the range of the node in the NETCONF interface information of the to-be-configured network element, for the network element to be configured, if The node component information (the foregoing ncd extended key field) in the reference NETCONF interface configuration packet has a component version of the to-be-configured network element, and the revision date of the corresponding module is not earlier than the enabled timestamp, and the reference is retained.
  • the NETCONF interface configures the corresponding node in the packet, otherwise the corresponding node is deleted.
  • the clipping algorithm used by the packet cutting unit in this embodiment is as follows:
  • the track-group-name node is configured in the component ZXROSNG V3.00.31 and the component ZXROSNG V2.00.32.
  • the configuration packet cutting unit does not need to modify the configuration packet of the reference NETCONF interface.
  • the up-delay node is only in the component ZXROSNG V3.00.31.
  • the configuration message delivery unit sends a NETCONF interface configuration packet to the NE that contains the component ZXROSNG V2.00.32, you need to configure the packet cutting unit pair.
  • the reference NETCONF interface configuration packet is trimmed, and the up-delay node that is not supported by the component ZXROSNG V2.00.32 is deleted.
  • the NETCONF interface configuration packet after the packet clipping unit is configured is as follows:
  • the configuration data pushing device of the present embodiment acquires network interface information of each network element to be configured, and generates reference network interface information according to the acquired network interface information of each network element to be configured; and generates data according to the reference network interface information.
  • the first network interface configuration packet carrying the configuration data; the network interface information of each of the to-be-configured network elements, and the first network interface configuration packet, Matching and sending a corresponding second network interface configuration packet for each to-be-configured network element.
  • the module of each component version of the network element is statically merged as the basis for the configuration data sent by the network management system, and the packet is configured on the carrier NETCONF interface of the configuration data by using the network interface information of the corresponding module.
  • the dynamic adjustment is performed, and the NETCONF interface configuration packet conforming to the network element branch is correctly delivered, which reduces the number of interactions between the network management system and the network element, so that the embodiment of the present invention can improve the efficiency of configuration data push.
  • the NE to be configured parses the configuration data carried by the NETCONF interface configuration packet and responds. For example, after the network element to be configured that includes the component ZXROSNG V2.00.32 receives the NETCONF interface configuration packet sent by the network management system, the configuration data is parsed: ⁇ track-group-name>test ⁇ /track-group-name> and ⁇ Up-delay>0 ⁇ /up-delay>, because the aforementioned configuration data is for the zxr10-samgr module included, the value of the zxr10-samgr module track-group-name node is set to test, and the value of the up-delay node is Set to 0.
  • the NETCONF response packet is generated based on the result of the configuration (successful or not), and the NETCONF response packet is returned to the NMS.
  • the NMS After receiving the NETCONF packet returned by the NE to be configured, the NMS receives the NETCONF packet. , the corresponding processing. The processing performed is implemented with reference to the NETCONF protocol standard, and is not described here.
  • the reference information generating module 10 is configured to: perform network interface information of each acquired network element to be configured. The compatibility check is performed; and when there is no conflict item, the reference network interface information is generated according to the obtained network interface information of each to-be-configured network element.
  • the reference information generating module 10 performs compatibility check on the acquired NETCONF interface information of each to-be-configured network element before combining the NETCONF interface information.
  • the reference information generating module 10 selects a module of a version component as a reference module (for example, a corresponding module of the first network element to be configured that accesses the network management system), and sequentially acquires the module of the other version component in the order of accessing the network management system.
  • the information node information in the NETCONF interface information
  • Optional Ground the check items for compatibility check are shown in Table 1:
  • module, namespace, prefix, belongs-to statement parameters can not be modified 2.
  • the basic type of the type clause of the same node (including typedef) cannot be modified. 3, the same node config meaning can not be modified 4, the same leaf node display definition units clause parameters can not be modified 5, the key clause of the list statement can not be added or the parameters change (including the order) 6, the unique clause of the list statement can not be added or the parameters can not be changed (including the order) 7, the value defined in the enum clause of the type enumeration can not conflict, the enumeration name can not be modified 8, the position defined by the bit in the type bits can not conflict, the name can not be modified 9, the path clause parameter of the type leafref can not be modified 10.
  • the base clause parameter of type identityref cannot be modified.
  • the configuration data pushing apparatus further includes a modifying module, which is configured to: when there is a conflicting item, the corresponding network interface The information is modified.
  • the modifying module performs modification processing on the NETCONF interface information with the conflicting item.
  • the modification module modifies the NETCONF interface information with conflicting items according to the constraint rule shown in Table 1, and eliminates the conflicting items.
  • the reference information generating module 10 performs the merging of the reference NETCONF interface information.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the module of each component version of the network element is statically merged, and the configuration data of the network management unit is dynamically adjusted, and the network configuration information of the corresponding module is dynamically adjusted by the network interface information of the corresponding module.
  • the NETCONF interface configuration packet matching the NE branch is delivered, which reduces the number of interactions between the NMS and the NE, thus improving the efficiency of configuration data push.

Abstract

本文公布一种配置数据推送方法及装置，所述配置数据推送方法包括：获取每个待配置网元的网络接口信息，并根据获取的每个待配置网元的网络接口信息生成基准网络接口信息；根据所述基准网络接口信息生成携带有配置数据的第一网络接口配置报文；根据所述每个待配置网元的网络接口信息，以及所述第一网络接口配置报文，为每个待配置网元匹配并发送对应的第二网络接口配置报文。

Description

配置数据推送方法及装置 技术领域
本申请涉及但不限于通信技术领域。
背景技术
针对简单网络管理协议(Simple Network Management Protocol，SNMP)的诸多缺陷，相关技术中提出了网络配置协议(Network Configuration Protocol，NETCONF)。NETCONF基本上解决了SNMP的缺点，适合大型且复杂的网络管理。YANG语言是一种抽象描述语言，YANG语言的功能强大、可读性好、信息完整、可扩展性强，是最适合NETCONF的数据建模语言。
目前，由于工程实际的需要，网元往往存在多个分支，同一个分支下，也有新老版本的网元。不同分支的网元，一个分支的新老版本之间，往往存在差异。当需要对网元进行批量配置时，网管需要针对不同的网元的差异生成针对性的配置数据，并以NETCONF接口配置报文的形式发放至每个网元，网管和网元之间需要多次交互，导致配置数据推送效率较低。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本文提供一种配置数据推送方法及配置，旨在提高配置数据推送的效率。
一种配置数据推送方法，所述配置数据推送方法包括：
获取每个待配置网元的网络接口信息，并根据获取的每个待配置网元的网络接口信息生成基准网络接口信息；
根据所述基准网络接口信息生成携带有配置数据的第一网络接口配置报文；
根据所述每个待配置网元的网络接口信息，以及所述第一网络接口配置报文，为每个待配置网元匹配并发送对应的第二网络接口配置报文。
可选地，所述根据获取的每个待配置网元的网络接口信息生成基准网络接口信息包括：
根据获取的每个待配置网元的网络接口信息中的关键字和/或扩展关键字，将获取的每个待配置网元的网络接口信息合并为基准网络接口信息。
可选地，所述根据所述每个待配置网元的网络接口信息，以及所述第一网络接口配置报文，为每个待配置网元匹配并发送对应的第二网络接口配置报文包括：
根据获取的每个待配置网元的网络接口信息中的关键字和/或扩展关键字，对所述第一网络接口配置报文进行裁剪，将裁剪后的第一网络接口配置报文作为第二网络接口配置报文；
将第二网络接口配置报文发送至对应的每个待配置网元。
可选地，所述根据获取的每个待配置网元的网络接口信息生成基准网络接口信息包括：
对获取的每个待配置网元的网络接口信息进行兼容性检查；
在不存在冲突项时，根据获取的每个待配置网元的网络接口信息生成基准网络接口信息。
可选地，所述对获取的每个待配置网元的网络接口信息进行兼容性检查的步骤之后，所述配置数据推送方法还包括：
在存在冲突项时，对相应的网络接口信息进行修改处理。
一种配置数据推送装置，所述配置数据推送装置包括：
基准信息生成模块，设置为：获取每个待配置网元的网络接口信息，并根据获取的每个待配置网元的网络接口信息生成基准网络接口信息；
配置报文生成模块，设置为：根据所述基准网络接口信息生成携带有配置数据的第一网络接口配置报文；
配置报文下发模块，设置为：根据所述每个待配置网元的网络接口信息，以及所述第一网络接口配置报文，为每个待配置网元匹配并发送对应的第二网络接口配置报文。
可选地，所述基准信息生成模块是设置为：根据获取的每个待配置网元的网络接口信息中的关键字和/或扩展关键字，将获取的每个待配置网元的网络接口信息合并为基准网络接口信息。
可选地，所述配置报文下发模块包括：
配置报文裁剪单元，设置为：根据获取的每个待配置网元的网络接口信息中的关键字和/或扩展关键字，对所述第一网络接口配置报文进行裁剪，将裁剪后的第一网络接口配置报文作为第二网络接口配置报文；
配置报文下发单元，设置为：将第二网络接口配置报文发送至对应的每个待配置网元。
可选地，所述基准信息生成模块是设置为：对获取的每个待配置网元的网络接口信息进行兼容性检查；以及在不存在冲突项时，根据获取的每个待配置网元的网络接口信息生成基准网络接口信息。
可选地，所述配置数据推送装置还包括修改模块，设置为：在存在冲突项时，对相应的网络接口信息进行修改处理。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任一项的方法。
本发明实施例通过获取每个待配置网元的网络接口信息，并根据获取的每个待配置网元的网络接口信息生成基准网络接口信息；根据所述基准网络接口信息生成携带有配置数据的第一网络接口配置报文；根据所述每个待配置网元的网络接口信息，以及所述第一网络接口配置报文，为每个待配置网元匹配并发送对应的第二网络接口配置报文。相较于相关技术，本发明实施例通过静态的合并网元每个组件版本的模块，作为网管下发配置数据的依据，并通过相应模块的网络接口信息对配置数据的载体NETCONF接口配置报文进行动态调整，正确的下发符合网元分支的NETCONF接口配置报文， 降低了网管和网元之间的交互次数，从而提高配置数据推送的效率。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1为本发明配置数据推送方法第一实施例的流程示意图；
图2为图1中生成基准网络接口信息的细化流程示意图；
图3为本发明配置数据推送装置第一实施例的功能模块示意图。
本发明的实施方式
本发明实施例提供一种配置数据推送方法，参照图1，在本发明配置数据推送方法的第一实施例中，所述配置数据推送方法包括：
S10，获取每个待配置网元的网络接口信息，并根据获取的每个待配置网元的网络接口信息生成基准网络接口信息；
网元就是组成网络的网络设备，包括服务器、客户端、路由器以及交换机等。在实际应用中，一个网元往往包括多个组件，每个组件有不同的版本，不同版本的组件包括多个模块，其中每个版本中的模块有着独立的演化机制。在运行NETCONF(Network Configuration Protocol，网络配置协议)的网络中，NETCONF接口用于功能性的描述模块，其符合YANG模型规范。YANG(RFC6020)语言规定了一个模块的组成结构：它主要包括头信息、链接信息、元信息、修订信息和模块主体信息。其中，头信息定义了模块的标识，模块主体信息包含了本模块和/或其它模块定义的结构(typedef、extension以及feature等)，以及本模块的自定义结构(container、choice、case、list以及leaf等)，自定义结构规定了该模块的管理范围信息。以下以运行NETCONF的网络进行说明。
任意网元可通过向网管(网元的一种，用于控制待配置网元的运行)发送配置请求的方式，成为网管的待配置网元，以接受网管的管理。在任意时刻，网管只要接收到配置请求，均会将该配置请求对应的网元标记为待配置网元。任意网元在成为网管的待配置网元之后，周期向网管发送Hello报文， 所述Hello报文是符合NETCONF协议规范的XML报文，其用于维持待配置网元和网管的管理关系，携带有待配置网元的NETCONF接口信息，NETCONF接口信息中通告有组件信息；网管在接收到每个待配置网元的Hello报文后，将Hello报文通告的组件信息与本地存储的组件数据库中的每个组件信息进行比对，当待配置网元的Hello报文通告的组件信息在组件数据库中均存在匹配项时，网管识别该网元在管理范围内；当待配置网元的Hello报文通告的任一组件信息在组件数据库中不存在匹配项时，网管识别该网元不在管理范围内，断开与该网元的连接，拒绝管理。
在基于网管和待配置网元组成的网络中，网管在接收到每个待配置网元发送的Hello报文后，解析其接收到的每个Hello报文，获取每个待配置网元的NETCONF接口信息(网络接口信息)，所述NETCONF接口信息描述了其对应待配置网元的每个模块。其中网管和待配置网元之间的通信基于RPC(Remote Procedure Call，远程过程调用)实现。网管运行NETCONF客户端，待配置网元运行NETCONF服务器端。
在获取到每个待配置网元的NETCONF接口信息后，网管根据获取的每个待配置网元的NETCONF接口信息生成基准NETCONF接口信息(基准网络接口信息)，通俗的说，就是把每个NETCONF接口合并成一个大而全的NETCONF接口。其中，所述根据获取的每个待配置网元的网络接口信息生成基准网络接口信息包括：
根据获取的每个待配置网元的NETCONF接口信息中的关键字和/或扩展关键字，将获取的每个待配置网元的NETCONF接口信息合并为基准NETCONF接口信息。
其中，合并是指结合NETCONF接口信息中关键字和/或扩展关键字的含义，按照指导原则，对多个版本的相同模块的模块主体信息部分进行语义分析并进行合并(包含节点合并以及节点约束的合并)。
选取一个版本组件的模块作为基准模块(例如为第一个接入网管的待配置网元的相应模块)，依次(接入网管的顺序)获取其它版本组件的该模块信息，通过前序遍历的方式在基准模块对应的NETCONF接口信息中查找相同节点，若不存在，则在基准模块对应的NETCONF接口信息中添加相关节点。 可选地，本实施例的合并算法如下所示：
void preorder(baseModule,module,errors)
{
path＝getAbsolutePath(module)
node＝lookup(baseModule,path)
if node is None
{
parent_path＝getAbsolutePath(module.parent)
parent＝lookup(baseModule,parent_path)
parent.addChild(module)
}
else
{
//找到相应的规则
rule＝match(node,module)
rule.check(errors)
rule.action()
}
for(child in module)
{
preorder(baseModule,child,errors)；
}
}
合并得到的基准NETCONF接口信息将会增加一个ncd:device-availabledate扩展关键字来标记模块主体自定义节点范围。形象的说，我们把单个模块管理的范围看作一棵多叉树，使用组件名、组件版本以及启用时间戳这样一个三元组来标记多叉树上的节点，记录有效的组件信息。以下以组件ZXROSNG V2.00.32和ZXROSNG V3.00.31的zxr10-samgr模块 为例说明：
若track-group-name节点在两个版本的组件中都存在，则基准NETCONF接口信息将用两个ncd:device-availabledate子句说明该节点支持的范围，如下所示：
Figure PCTCN2016072487-appb-000001
若up-delay节点只存在于ZXROSNG V3.00.31中，则基准NETCONF接口信息包含了该节点，且用ncd:device-availabledate子句来说明这个节点只在ZXROSNG V3.00.31中支持，如下所示：
Figure PCTCN2016072487-appb-000002
Figure PCTCN2016072487-appb-000003
S20，根据所述基准网络接口信息生成携带有配置数据的第一网络接口配置报文；
本实施例中，按照NETCONF协议标准，根据基准NETCONF接口信息生成基准NETCONF接口配置报文(第一网络接口配置报文)，生成的所述基准NETCONF接口配置报文是符合NETCONF协议规范的XML报文，其携带有配置数据，用于进行待配置网元相应NETCONF接口的配置。其中，基准NETCONF接口配置报文的生成过程按照NETCONF协议标准施行，此处不再赘述。例如，基于上述基准NETCONF接口信息生成的基准NETCONF接口配置报文如下所示：
Figure PCTCN2016072487-appb-000004
Figure PCTCN2016072487-appb-000005
上述基准NETCONF接口配置报文同时包括了track-group-name节点和up-delay节点的配置数据。
S30，根据所述每个待配置网元的网络接口信息，以及所述第一网络接口配置报文，为每个待配置网元匹配并发送对应的第二网络接口配置报文。
本实施例中，在生成基准NETCONF接口配置报文后，根据所述每个待配置网元的NETCONF接口信息，以及所述基准NETCONF接口配置报文，为每个待配置网元匹配并发送对应的NETCONF接口配置报文(第二网络接口配置报文)。可基于每个待配置网元的NETCONF接口信息，从所述基准NETCONF接口配置报文中取出部分数据作为所述NETCONF接口配置报文；或者裁剪掉所述基准NETCONF接口配置报文中无用部分，将裁剪后的基准NETCONF接口配置报文作为所述NETCONF接口配置报文。
可选地，在本实施例中，根据获取的每个待配置网元的NETCONF接口信息中的关键字和/或扩展关键字，对所述基准NETCONF接口配置报文进行裁剪，将裁剪后的基准NETCONF接口配置报文作为对应每个待配置网元的NETCONF接口配置报文；
将NETCONF接口配置报文发送至对应的每个待配置网元。
裁剪是指将所述基准NETCONF接口配置报文与每个待配置网元NETCONF接口信息的功能集相比对，针对某待配置网元，删除其不支持的功能集，动态的裁剪出符合该待配置网元版本模块的NETCONF接口配置报文。其中，针对某待配置网元，将根据基准NETCONF接口信息生成的基准NETCONF接口配置报文中的节点范围与该待配置网元的NETCONF接口信息中节点的范围相比较，如果所述基准NETCONF接口配置报文中的节点组件信息(前述ncd扩展关键字段)存在该待配置网元通告的组件版本，并且相应模块的修订日期不早于启用时间戳，则保留所述基准NETCONF接口配置报文中相应节点，否则删除相应节点，可选地，本实施例采用的裁剪算法 如下所示：
1、建立节点的生效范围映射关系，形如(组件名称，组件版本)-->启用日期的数据字典，例如(ZXROSNG,V2.00.32)-->2015-01-01；
2、若节点的生效范围为空，保留；
3、比较NETCONF接口配置报文中节点的组件信息中是否存在网元通告的组件版本。若存在，保留；否则，裁剪；
4、比较相应模块的修订字段的日期是否早于启用时间戳，是则裁剪；否则，保留。
由于track-group-name节点在组件ZXROSNG V3.00.31和组件ZXROSNG V2.00.32中均存在，不需要对所述基准NETCONF接口配置报文进行裁剪，可直接下发；而up-delay节点只存在于组件ZXROSNG V3.00.31中，针对包含组件ZXROSNG V2.00.32的网元下发NETCONF接口配置报文时，需要对基准NETCONF接口配置报文进行裁剪，删除组件ZXROSNG V2.00.32不支持的up-delay节点，裁剪后的NETCONF接口配置报文如下所示：
Figure PCTCN2016072487-appb-000006
容易看出的是，与裁剪前的基准NETCONF接口配置报文相比，裁剪后的基准NETCONF接口配置报文删除了“<up-delay>0</up-delay>”字段，即删 除了组件ZXROSNG V2.00.32不支持的up-delay节点。
本实施例提出的配置数据推送方法，获取每个待配置网元的网络接口信息，并根据获取的每个待配置网元的网络接口信息生成基准网络接口信息；根据所述基准网络接口信息生成携带有配置数据的第一网络接口配置报文；根据所述每个待配置网元的网络接口信息，以及所述第一网络接口配置报文，为每个待配置网元匹配并发送对应的第二网络接口配置报文。相较于相关技术，本发明实施例通过静态的合并网元每个组件版本的模块，作为网管下发配置数据的依据，并通过相应模块的网络接口信息对配置数据的载体NETCONF接口配置报文进行动态调整，正确的下发符合网元分支的NETCONF接口配置报文，降低了网管和网元之间的交互次数，从而本发明实施例能够提高配置数据推送的效率。
此外，待配置网元在接收到网管发送的NETCONF接口配置报文之后，解析出其接收到NETCONF接口配置报文所携带的配置数据，并响应。例如，前述包括组件ZXROSNG V2.00.32的待配置网元在接收到网管发送的NETCONF接口配置报文后，解析出配置数据：<track-group-name>test</track-group-name>和<up-delay>0</up-delay>，由于前述配置数据针对其包括的zxr10-samgr模块，则将zxr10-samgr模块track-group-name节点的值设为test，将up-delay节点的值设为0。待配置网元在完成相应的配置后，基于配置的结果(成功与否)生成NETCONF回应报文，并将NETCONF回应报文返回至网管；网管在接收到待配置网元返回的NETCONF报文后，进行相应的处理。其中，进行的处理参照NETCONF协议标准施行，此处不再赘述。
基于第一实施例，提出本发明配置数据推送方法的第二实施例，参照图2，在本实施例中，上述步骤S10中根据获取的每个待配置网元的网络接口信息生成基准网络接口信息包括：
S101，对获取的每个待配置网元的网络接口信息进行兼容性检查；
S102，在不存在冲突项时，根据获取的每个待配置网元的网络接口信息生成基准网络接口信息。
本实施例中，为进一步提升配置数据的推送效率，在合并基准NETCONF接口信息之前，对获取的每个待配置网元的NETCONF接口信息进行兼容性检查。其中，选取一个版本组件的模块作为基准模块(例如为第一个接入网管的待配置网元的相应模块)，依次(接入网管的顺序)获取其它版本组件的该模块信息(NETCONF接口信息中的节点信息)，通过前序遍历的方式在基准模块对应的NETCONF接口信息中查找相同节点，若存在相同节点，则进行兼容性检查，并记录冲突信息。可选地，兼容性检查的检查项如表1所示：
1、module、namespace、prefix、belongs-to语句的参数不能修改
2、相同节点(含typedef)的type子句的基本类型不能修改
3、相同节点的config含义不能修改
4、相同leaf节点的显示定义units子句参数不能修改
5、list语句的key子句不能添加或参数发生变化(包括顺序)
6、list语句的unique子句不能增加或参数不能变化(包括顺序)
7、类型enumeration中enum子句定义的value不能冲突，枚举名称不能修改
8、类型bits中bit定义的position不能冲突，名称不能修改
9、类型leafref的path子句参数不能修改
10、类型identityref的base子句参数不能修改
基于第二实施例，提出本发明配置数据推送方法的第三实施例，在本实施例中，上述步骤S101之后，所述配置数据推送方法还包括：
在存在冲突项时，对相应的网络接口信息进行修改处理。
本实施例中，若在完成兼容性检查后，发现存在冲突项，则对存在冲突项的NETCONF接口信息进行修改处理。其中，按照表1所示的约束规则对存在冲突项的NETCONF接口信息进行修改，消除冲突项。在完成对存在冲突项的NETCONF接口信息的修改后，进行基准NETCONF接口信息的合并。
本发明实施例还提供一种配置数据推送装置，参照图3，在本发明配置数据推送装置的第一实施例中，所述配置数据推送装置包括：
基准信息生成模块10，设置为：获取每个待配置网元的网络接口信息，并根据获取的每个待配置网元的网络接口信息生成基准网络接口信息；
网元就是组成网络的网络设备，包括服务器、客户端、路由器以及交换机等。在实际应用中，一个网元往往包括多个组件，每个组件有不同的版本，不同版本的组件包括多个模块，其中每个版本中的模块有着独立的演化机制。在运行NETCONF(Network Configuration Protocol，网络配置协议)的网络中，NETCONF接口用于功能性的描述模块，其符合YANG模型规范。YANG(RFC6020)语言规定了一个模块的组成结构：它主要包括头信息、链接信息、元信息、修订信息和模块主体信息。其中，头信息定义了模块的标识，模块主体信息包含了本模块和/或其它模块定义的结构(typedef、extension以及feature等)，以及本模块的自定义结构(container、choice、case、list以及leaf等)，自定义结构规定了该模块的管理范围信息。以下以运行NETCONF的网络进行说明。
任意网元可通过向网管(网元的一种，用于控制待配置网元的运行)发送配置请求的方式，成为网管的待配置网元，以接受网管的管理。在任意时刻，网管只要接收到配置请求，均会将该配置请求对应的网元标记为待配置网元。任意网元在成为网管的待配置网元之后，周期向网管发送Hello报文，所述Hello报文是符合NETCONF协议规范的XML报文，其用于维持待配置网元和网管的管理关系，携带有待配置网元的NETCONF接口信息，NETCONF接口信息中通告有组件信息；网管在接收到到每个待配置网元的Hello报文后，将Hello报文通告的组件信息与本地存储的组件数据库中的每个组件信息进行比对，当待配置网元的Hello报文通告的组件信息在组件数据库中均存在匹配项时，网管识别该网元在管理范围内；当待配置网元的Hello报文通告的任一组件信息在组件数据库中不存在匹配项时，网管识别该网元不在管理范围内，断开与该网元的连接，拒绝管理。
在基于网管和待配置网元组成的网络中，本实施例提供的配置数据推送装置内置于网管运行，其中，基准信息生成模块10在网管接收到每个待配置网元发送的Hello报文后，解析网管接收到的每个Hello报文，获取每个待配置网元的NETCONF接口信息(网络接口信息)，所述NETCONF接口信息描述了其对应待配置网元的每个模块。其中网管和待配置网元之间的通信基于RPC(Remote Procedure Call，远程过程调用)实现。网管运行NETCONF 客户端，待配置网元运行NETCONF服务器端。
在获取到每个待配置网元的NETCONF接口信息后，基准信息生成模块10根据获取的每个待配置网元的NETCONF接口信息生成基准NETCONF接口信息(基准网络接口信息)，通俗的说，就是把每个NETCONF接口合并成一个大而全的NETCONF接口。其中，所述基准信息生成模块10是设置为：根据获取的每个待配置网元的NETCONF接口信息中的关键字和/或扩展关键字，将获取的每个待配置网元的NETCONF接口信息合并为基准NETCONF接口信息。
其中，合并是指结合NETCONF接口信息中关键字和/或扩展关键字的含义，按照指导原则，对多个版本的相同模块的模块主体信息部分进行语义分析并进行合并(包含节点合并以及节点约束的合并)。
基准信息生成模块10选取一个版本组件的模块作为基准模块(例如为第一个接入网管的待配置网元的相应模块)，依次(接入网管的顺序)获取其它版本组件的该模块信息，通过前序遍历的方式在基准模块对应的NETCONF接口信息中查找相同节点，若不存在，则在基准模块对应的NETCONF接口信息中添加相关节点。可选地，本实施例的合并算法如下所示：
void preorder(baseModule,module,errors)
{
path＝getAbsolutePath(module)
node＝lookup(baseModule,path)
if node is None
{
parent_path＝getAbsolutePath(module.parent)
parent＝lookup(baseModule,parent_path)
parent.addChild(module)
}
else
{
//找到相应的规则
rule＝match(node,module)
rule.check(errors)
rule.action()
}
for(child in module)
{
preorder(baseModule,child,errors)；
}
}
基准信息生成模块10合并得到的基准NETCONF接口信息将会增加一个ncd:device-availabledate扩展关键字来标记模块主体自定义节点范围。形象的说，我们把单个模块管理的范围看作一棵多叉树，使用组件名、组件版本以及启用时间戳这样一个三元组来标记多叉树上的节点，记录有效的组件信息。以下以组件ZXROSNG V2.00.32和ZXROSNG V3.00.31的zxr10-samgr模块为例说明：
若track-group-name节点在两个版本的组件中都存在，则基准NETCONF接口信息将用两个ncd:device-availabledate子句说明该节点支持的范围，如下所示：
Figure PCTCN2016072487-appb-000007
Figure PCTCN2016072487-appb-000008
若up-delay节点只存在于ZXROSNG V3.00.31中，则基准NETCONF接口信息包含了该节点，且用ncd:device-availabledate子句来说明这个节点只在ZXROSNG V3.00.31中支持，如下所示：
Figure PCTCN2016072487-appb-000009
配置报文生成模块20，设置为：根据所述基准网络接口信息生成携带有配置数据的第一网络接口配置报文；
本实施例中，配置报文生成模块20按照NETCONF协议标准，根据基准NETCONF接口信息生成基准NETCONF接口配置报文(第一网络接口配置报文)，生成的所述基准NETCONF接口配置报文是符合NETCONF协议规范的XML报文，其携带有配置数据，用于进行待配置网元相应NETCONF接口的配置。其中，基准NETCONF接口配置报文的生成过程按照NETCONF协议标准施行，此处不再赘述。例如，基于上述基准NETCONF接口信息生成的基准NETCONF接口配置报文如下所示：
Figure PCTCN2016072487-appb-000010
上述基准NETCONF接口配置报文同时包括了track-group-name节点和up-delay节点的配置数据。
配置报文下发模块30，设置为：根据所述每个待配置网元的网络接口信息，以及所述第一网络接口配置报文，为每个待配置网元匹配并发送对应的第二网络接口配置报文。
本实施例中，在配置报文生成模块20生成基准NETCONF接口配置报文后，配置报文下发模块30根据所述每个待配置网元的NETCONF接口信息，以及所述基准NETCONF接口配置报文，为每个待配置网元匹配并发送对应 的NETCONF接口配置报文(第二网络接口配置报文)。配置报文下发模块30可基于每个待配置网元的NETCONF接口信息，从所述基准NETCONF接口配置报文中取出部分数据作为所述NETCONF接口配置报文；或者裁剪掉所述基准NETCONF接口配置报文中无用部分，将裁剪后的基准NETCONF接口配置报文作为所述NETCONF接口配置报文。
可选地，在本实施例中，所述配置报文下发模块30包括：
配置报文裁剪单元，设置为：根据获取的每个待配置网元的NETCONF接口信息中的关键字和/或扩展关键字，对所述基准NETCONF接口配置报文进行裁剪，将裁剪后的基准NETCONF接口配置报文作为对应每个待配置网元的NETCONF接口配置报文；
配置报文下发单元，设置为：将NETCONF接口配置报文发送至对应的每个待配置网元。
裁剪是指将所述基准NETCONF接口配置报文与每个待配置网元NETCONF接口信息的功能集相比对，针对某待配置网元，删除其不支持的功能集，动态的裁剪出符合该待配置网元版本模块的NETCONF接口配置报文。其中，配置报文裁剪单元针对某待配置网元，将根据基准NETCONF接口信息生成的基准NETCONF接口配置报文中的节点范围与该待配置网元的NETCONF接口信息中节点的范围相比较，如果所述基准NETCONF接口配置报文中的节点组件信息(前述ncd扩展关键字段)存在该待配置网元通告的组件版本，并且相应模块的修订日期不早于启用时间戳，则保留所述基准NETCONF接口配置报文中相应节点，否则删除相应节点，可选地，本实施例配置报文裁剪单元采用的裁剪算法如下所示：
1、建立节点的生效范围映射关系，形如(组件名称，组件版本)-->启用日期的数据字典，例如(ZXROSNG,V2.00.32)-->2015-01-01；
2、若节点的生效范围为空，保留；
3、比较NETCONF接口配置报文中节点的组件信息中是否存在网元通告的组件版本。若存在，保留；否则，裁剪；
4、比较相应模块的修订字段的日期是否早于启用时间戳，是则裁剪；否 则，保留。
由于track-group-name节点在组件ZXROSNG V3.00.31和组件ZXROSNG V2.00.32中均存在，配置报文裁剪单元不需要对所述基准NETCONF接口配置报文进行裁剪，配置报文下发单元可直接下发；而up-delay节点只存在于组件ZXROSNG V3.00.31中，配置报文下发单元针对包含组件ZXROSNG V2.00.32的网元下发NETCONF接口配置报文时，需要配置报文裁剪单元对基准NETCONF接口配置报文进行裁剪，删除组件ZXROSNG V2.00.32不支持的up-delay节点，配置报文裁剪单元裁剪后的NETCONF接口配置报文如下所示：
Figure PCTCN2016072487-appb-000011
容易看出的是，与裁剪前的基准NETCONF接口配置报文相比，裁剪后的基准NETCONF接口配置报文删除了“<up-delay>0</up-delay>”字段，即删除了组件ZXROSNG V2.00.32不支持的up-delay节点。
本实施例提出的配置数据推送装置，获取每个待配置网元的网络接口信息，并根据获取的每个待配置网元的网络接口信息生成基准网络接口信息；根据所述基准网络接口信息生成携带有配置数据的第一网络接口配置报文；根据所述每个待配置网元的网络接口信息，以及所述第一网络接口配置报文， 为每个待配置网元匹配并发送对应的第二网络接口配置报文。相较于相关技术，本发明实施例通过静态的合并网元每个组件版本的模块，作为网管下发配置数据的依据，并通过相应模块的网络接口信息对配置数据的载体NETCONF接口配置报文进行动态调整，正确的下发符合网元分支的NETCONF接口配置报文，降低了网管和网元之间的交互次数，从而本发明实施例能够提高配置数据推送的效率。
此外，待配置网元在接收到网管发送的NETCONF接口配置报文之后，解析出其接收到NETCONF接口配置报文所携带的配置数据，并响应。例如，前述包括组件ZXROSNG V2.00.32的待配置网元在接收到网管发送的NETCONF接口配置报文后，解析出配置数据：<track-group-name>test</track-group-name>和<up-delay>0</up-delay>，由于前述配置数据针对其包括的zxr10-samgr模块，则将zxr10-samgr模块track-group-name节点的值设为test，将up-delay节点的值设为0。待配置网元在完成相应的配置后，基于配置的结果(成功与否)生成NETCONF回应报文，并将NETCONF回应报文返回至网管；网管在接收到待配置网元返回的NETCONF报文后，进行相应的处理。其中，进行的处理参照NETCONF协议标准施行，此处不再赘述。
基于第一实施例，提出本发明配置数据推送装置的第二实施例，在本实施例中，所述基准信息生成模块10是设置为：对获取的每个待配置网元的网络接口信息进行兼容性检查；以及在不存在冲突项时，根据获取的每个待配置网元的网络接口信息生成基准网络接口信息。
本实施例中，为进一步提升配置数据的推送效率，基准信息生成模块10在合并NETCONF接口信息之前，对获取的每个待配置网元的NETCONF接口信息进行兼容性检查。其中，基准信息生成模块10选取一个版本组件的模块作为基准模块(例如为第一个接入网管的待配置网元的相应模块)，依次(接入网管的顺序)获取其它版本组件的该模块信息(NETCONF接口信息中的节点信息)，通过前序遍历的方式在基准模块对应的NETCONF接口信息中查找相同节点，若存在相同节点，则进行兼容性检查，并记录冲突信息。可选 地，兼容性检查的检查项如表1所示：
1、module、namespace、prefix、belongs-to语句的参数不能修改
2、相同节点(含typedef)的type子句的基本类型不能修改
3、相同节点的config含义不能修改
4、相同leaf节点的显示定义units子句参数不能修改
5、list语句的key子句不能添加或参数发生变化(包括顺序)
6、list语句的unique子句不能增加或参数不能变化(包括顺序)
7、类型enumeration中enum子句定义的value不能冲突，枚举名称不能修改
8、类型bits中bit定义的position不能冲突，名称不能修改
9、类型leafref的path子句参数不能修改
10、类型identityref的base子句参数不能修改
基于第二实施例，提出本发明配置数据推送装置的第三实施例，在本实施例中，所述配置数据推送装置还包括修改模块，设置为：在存在冲突项时，对相应的网络接口信息进行修改处理。本实施例中，若在基准信息生成模块10完成兼容性检查后，发现存在冲突项，则修改模块对存在冲突项的NETCONF接口信息进行修改处理。其中，修改模块按照表1所示的约束规则对存在冲突项的NETCONF接口信息进行修改，消除冲突项。在修改模块完成对存在冲突项的NETCONF接口信息的修改后，基准信息生成模块10进行基准NETCONF接口信息的合并。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
本发明实施例通过静态的合并网元每个组件版本的模块，作为网管下发配置数据的依据，并通过相应模块的网络接口信息对配置数据的载体NETCONF接口配置报文进行动态调整，正确的下发符合网元分支的NETCONF接口配置报文，降低了网管和网元之间的交互次数，从而提高配置数据推送的效率。

Claims (11)

  1. 一种配置数据推送方法，所述配置数据推送方法包括：
    获取每个待配置网元的网络接口信息，并根据获取的每个待配置网元的网络接口信息生成基准网络接口信息；
    根据所述基准网络接口信息生成携带有配置数据的第一网络接口配置报文；
    根据所述每个待配置网元的网络接口信息，以及所述第一网络接口配置报文，为每个待配置网元匹配并发送对应的第二网络接口配置报文。
  2. 如权利要求1所述的配置数据推送方法，其中，所述根据获取的每个待配置网元的网络接口信息生成基准网络接口信息包括：
    根据获取的每个待配置网元的网络接口信息中的关键字和/或扩展关键字，将获取的每个待配置网元的网络接口信息合并为基准网络接口信息。
  3. 如权利要求2所述的配置数据推送方法，其中，所述根据所述每个待配置网元的网络接口信息，以及所述第一网络接口配置报文，为每个待配置网元匹配并发送对应的第二网络接口配置报文包括：
    根据获取的每个待配置网元的网络接口信息中的关键字和/或扩展关键字，对所述第一网络接口配置报文进行裁剪，将裁剪后的第一网络接口配置报文作为第二网络接口配置报文；
    将第二网络接口配置报文发送至对应的每个待配置网元。
  4. 如权利要求1-3任一项所述的配置数据推送方法，其中，所述根据获取的每个待配置网元的网络接口信息生成基准网络接口信息包括：
    对获取的每个待配置网元的网络接口信息进行兼容性检查；
    在不存在冲突项时，根据获取的每个待配置网元的网络接口信息生成基准网络接口信息。
  5. 如权利要求4所述的配置数据推送方法，其中，所述对获取的每个待配置网元的网络接口信息进行兼容性检查的步骤之后，所述配置数据推送方法还包括：
    在存在冲突项时，对相应的网络接口信息进行修改处理。
  6. 一种配置数据推送装置，所述配置数据推送装置包括：
    基准信息生成模块，设置为：获取每个待配置网元的网络接口信息，并根据获取的每个待配置网元的网络接口信息生成基准网络接口信息；
    配置报文生成模块，设置为：根据所述基准网络接口信息生成携带有配置数据的第一网络接口配置报文；
    配置报文下发模块，设置为：根据所述每个待配置网元的网络接口信息，以及所述第一网络接口配置报文，为每个待配置网元匹配并发送对应的第二网络接口配置报文。
  7. 如权利要求6所述的配置数据推送装置，其中，所述基准信息生成模块是设置为：根据获取的每个待配置网元的网络接口信息中的关键字和/或扩展关键字，将获取的每个待配置网元的网络接口信息合并为基准网络接口信息。
  8. 如权利要求7所述的配置数据推送装置，其中，所述配置报文下发模块包括：
    配置报文裁剪单元，设置为：根据获取的每个待配置网元的网络接口信息中的关键字和/或扩展关键字，对所述第一网络接口配置报文进行裁剪，将裁剪后的第一网络接口配置报文作为第二网络接口配置报文；
    配置报文下发单元，设置为：将第二网络接口配置报文发送至对应的每个待配置网元。
  9. 如权利要求6-8任一项所述的配置数据推送装置，其中，所述基准信息生成模块是设置为：对获取的每个待配置网元的网络接口信息进行兼容性检查；以及在不存在冲突项时，根据获取的每个待配置网元的网络接口信息生成基准网络接口信息。
  10. 如权利要求9所述的配置数据推送装置，其中，所述配置数据推送装置还包括修改模块，设置为：在存在冲突项时，对相应的网络接口信息进行修改处理。
  11. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-5任一项的方法。
PCT/CN2016/072487 2015-06-19 2016-01-28 配置数据推送方法及装置 WO2016201988A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510347299.2 2015-06-19
CN201510347299.2A CN106257868B (zh) 2015-06-19 2015-06-19 配置数据推送方法及装置

Publications (1)

Publication Number Publication Date
WO2016201988A1 true WO2016201988A1 (zh) 2016-12-22

Family

ID=57544841

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/072487 WO2016201988A1 (zh) 2015-06-19 2016-01-28 配置数据推送方法及装置

Country Status (2)

Country Link
CN (1) CN106257868B (zh)
WO (1) WO2016201988A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113111223A (zh) * 2021-04-26 2021-07-13 银清科技有限公司 报文生成xml串的方法及装置

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109144489B (zh) * 2017-06-16 2021-11-05 上海赛特斯信息科技股份有限公司 基于Yang语言模型的状态数据处理方法
CN112583630B (zh) 2019-09-29 2022-07-12 华为技术有限公司 设备管理方法、装置、系统、设备及存储介质
CN112751698B (zh) * 2019-10-31 2023-10-24 华为技术有限公司 设备管理方法、装置、系统、设备及存储介质
CN113438100B (zh) * 2021-06-07 2023-07-18 江西山水光电科技股份有限公司 一种基于netconf协议的网络设备配置同步和上载方法
CN113542034B (zh) * 2021-07-28 2024-03-19 山石网科通信技术股份有限公司 网元信息处理系统、网元管理方法及装置
CN114205205A (zh) * 2022-02-15 2022-03-18 北京华环电子股份有限公司 一种兼容不同yang模型的南向接口实现方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040006608A1 (en) * 2002-07-08 2004-01-08 Convergys Cmg Utah Flexible network element interface
CN101442469A (zh) * 2007-11-22 2009-05-27 中国移动通信集团公司 下发配置数据的方法、系统及装置
CN101834742A (zh) * 2010-05-06 2010-09-15 烽火通信科技股份有限公司 通过网管服务器远程配置网元的方法
CN102088721A (zh) * 2009-12-03 2011-06-08 中兴通讯股份有限公司 关联网元间对接参数配置错误的修复方法及其系统
CN102891768A (zh) * 2012-10-11 2013-01-23 华为技术有限公司 网络管理的方法和网元
US8948045B2 (en) * 2006-06-08 2015-02-03 Alcatel Lucent Communication system and method of configuring a communication interface

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1155201C (zh) * 2001-08-03 2004-06-23 华为技术有限公司 一种对通信设备进行数据配置的方法及系统
US9098558B2 (en) * 2013-04-01 2015-08-04 Oracle International Corporation Enhanced flexibility for users to transform XML data to a desired format
CN104079428B (zh) * 2014-04-01 2017-12-08 烽火通信科技股份有限公司 管理配置信息冲突的系统及方法
CN104579792A (zh) * 2015-01-26 2015-04-29 四川中电启明星信息技术有限公司 多适配方式实现多种类型虚拟资源集中管理架构及方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040006608A1 (en) * 2002-07-08 2004-01-08 Convergys Cmg Utah Flexible network element interface
US8948045B2 (en) * 2006-06-08 2015-02-03 Alcatel Lucent Communication system and method of configuring a communication interface
CN101442469A (zh) * 2007-11-22 2009-05-27 中国移动通信集团公司 下发配置数据的方法、系统及装置
CN102088721A (zh) * 2009-12-03 2011-06-08 中兴通讯股份有限公司 关联网元间对接参数配置错误的修复方法及其系统
CN101834742A (zh) * 2010-05-06 2010-09-15 烽火通信科技股份有限公司 通过网管服务器远程配置网元的方法
CN102891768A (zh) * 2012-10-11 2013-01-23 华为技术有限公司 网络管理的方法和网元

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113111223A (zh) * 2021-04-26 2021-07-13 银清科技有限公司 报文生成xml串的方法及装置
CN113111223B (zh) * 2021-04-26 2023-10-13 银清科技有限公司 报文生成xml串的方法及装置

Also Published As

Publication number Publication date
CN106257868B (zh) 2020-11-03
CN106257868A (zh) 2016-12-28

Similar Documents

Publication Publication Date Title
WO2016201988A1 (zh) 配置数据推送方法及装置
US8688686B2 (en) SQL queries for simple network management protocol management information base tables
US10476755B1 (en) Multi vendor device support in network management systems
KR101117396B1 (ko) 원격 디바이스에 콘텐츠를 렌더링하기 위한 플랫폼
JP5250616B2 (ja) 管理ツリー中の管理対象をアドレッシングする方法及びそれに関連する装置管理システム
CN101098248B (zh) 一种基于配置描述文件实现通用网络管理的方法及系统
EP3172866B1 (en) System and method for metadata enhanced inventory management of a communications system
US9361398B1 (en) Maintaining a relational database and its schema in response to a stream of XML messages based on one or more arbitrary and evolving XML schemas
CN105138592A (zh) 一种基于分布式架构的日志数据存储和检索方法
JP2006507580A (ja) 移動通信装置用の装置管理用ツリーの設定を可能にするオブジェクトを定義する方法および装置
US10853347B2 (en) Dependency-based metadata retrieval and update
US20170270157A1 (en) TCP/IP Network Automation and Orchestration Tools
CN110971438A (zh) 配置数据的方法及装置
US20180321706A1 (en) Timestamp Alignment Across a Plurality Of Computing Devices
WO2016074412A1 (zh) 基于网络配置协议进行兼容管理的方法、存储介质及设备
US9189486B2 (en) Autonomic generation of document structure in a content management system
US20230308348A1 (en) Server to support client data models from heterogeneous data sources
WO2016086612A1 (zh) 一种单板的软件管理方法、系统及计算机存储介质
CN104717082A (zh) 业务模型的适配方法及系统
WO2011085573A1 (zh) 管理实体文件的建立、更新方法以及管理装置
US20140304293A1 (en) Apparatus and Method for Query Based Replication of Database
KR20170125665A (ko) M2M/IoT 플랫폼에서의 시맨틱 정보 관리 방법
JP2008293506A (ja) 構造化文書データ更新方法及び情報提供サーバ
WO2019062850A1 (zh) 数据交互的方法、装置及设备
US11689418B2 (en) Sharing configuration resources for network devices among applications

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16810729

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16810729

Country of ref document: EP

Kind code of ref document: A1