CN107222321B - Configuration message sending method and device - Google Patents

Configuration message sending method and device Download PDF

Info

Publication number
CN107222321B
CN107222321B CN201610164075.2A CN201610164075A CN107222321B CN 107222321 B CN107222321 B CN 107222321B CN 201610164075 A CN201610164075 A CN 201610164075A CN 107222321 B CN107222321 B CN 107222321B
Authority
CN
China
Prior art keywords
configuration data
netconf
group
packet
identifier
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201610164075.2A
Other languages
Chinese (zh)
Other versions
CN107222321A (en
Inventor
雷歆
戴新宁
周赟
尹彬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201610164075.2A priority Critical patent/CN107222321B/en
Publication of CN107222321A publication Critical patent/CN107222321A/en
Application granted granted Critical
Publication of CN107222321B publication Critical patent/CN107222321B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/08—Configuration management of networks or network elements
    • 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/04—Network management architectures or arrangements
    • H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Communication Control (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application discloses a method and a device for sending configuration messages, wherein the method comprises the following steps: the network configuration NETCONF management equipment determines that the first NETCONF agent equipment supports grouping capability; the grouping capability is the capability of processing a NETCONF protocol message comprising public configuration data and grouping configuration data; the NETCONF management equipment generates a first NETCONF protocol message comprising public configuration data and N pieces of grouping configuration data; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data; and the NETCONF management equipment sends the first NETCONF protocol message to the first NETCONF agent equipment.

Description

Configuration message sending method and device
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for sending a configuration packet.
Background
The network configuration (NETCONF) protocol is a network management protocol based on the extensible Markup Language (XML), and provides a method for configuring and managing network devices. Fig. 1 is a schematic diagram of a typical NETCONF application scenario. In fig. 1, a NETCONF management device configures a downstream device that accesses a NETCONF proxy device through a NETCONF protocol. There may be multiple downstream devices, sometimes up to thousands of downstream devices, under the NETCONF proxy device. Under the current NETCONF protocol, configuration data contained in a configuration message sent by a NETCONF management device may be used to configure a downstream device or a group of downstream devices. If the configuration of each downstream device is different, the NETCONF management device needs to send a configuration message for each downstream device, but different configuration data corresponding to a plurality of downstream devices cannot be sent through one configuration message, which results in low efficiency of configuring and managing the network device.
Disclosure of Invention
The embodiment of the application provides a method and a device for sending a configuration message, which are used for solving the problem of low efficiency of configuring and managing network equipment in the prior art.
A first aspect of the present application provides a method for sending a configuration packet, including:
the network configuration NETCONF management equipment determines that the first NETCONF agent equipment supports grouping capability; the grouping capability is the capability of processing a NETCONF protocol message comprising public configuration data and grouping configuration data;
the NETCONF management equipment generates a first NETCONF protocol message comprising public configuration data and N pieces of grouping configuration data; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data;
and the NETCONF management equipment sends the first NETCONF protocol message to the first NETCONF agent equipment.
According to the method provided by the first aspect of the present application, after determining that the first NETCONF proxy device supports the packet capability, the NETCONF management device sends a first NETCONF protocol message to the first NETCONF proxy device, where the first NETCONF protocol message includes public configuration data and N packet configuration data. Since each group configuration data includes at least one group identification, the group configuration data is used for indicating the group configuration data to be configuration data which is exclusively shared by at least one group of downstream devices indicated by the at least one group identification; the common configuration data is configuration data shared by all groups of downstream devices indicated by all the group identifiers in the N group configuration data, and therefore, the configuration data of each group of downstream devices is composed of the common configuration data and all the group configuration data including the group identifiers of the group of downstream devices, so that different configuration data of different downstream devices are sent to the first NETCONF proxy device through the same first NETCONF protocol message, interaction times when the NETCONF management device configures the downstream devices managed by the first NETCONF proxy device are reduced, and efficiency of configuring and managing network devices is improved.
Optionally, the method of the first aspect further includes:
the NETCONF management equipment determines that second NETCONF agent equipment does not support grouping capability, and then K second NETCONF protocol messages are generated; each second NETCONF protocol message comprises independent configuration data and a group identifier or an equipment identifier corresponding to the independent configuration data; the independent configuration data is configuration data which is exclusively shared by a group of downstream devices indicated by the group identification or configuration data which is exclusively shared by the downstream devices indicated by the device identification;
and the NETCONF management equipment sends the K second NETCONF protocol messages to the second NETCONF agent equipment.
In the method, when determining that the second NETCONF proxy equipment does not support the grouping capability, the NETCONF management equipment generates and sends K second NETCONF protocol messages. The second NETCONF protocol message is in the format of the NETCONF protocol message in the prior art, so that NETCONF management equipment can interact with second NETCONF proxy equipment which does not support grouping capability, and the compatibility of the equipment is improved.
Optionally, the public configuration data and the N pieces of packet configuration data are located in a configuration data node domain in a content layer of the first NETCONF protocol packet.
Optionally, the method of the first aspect further includes: the NETCONF management equipment sends a third NETCONF protocol message comprising public configuration data and L grouping identifiers to the first NETCONF agent equipment; wherein, L is a natural number, the public configuration data is located in a configuration data node domain of a content layer of the third NETCONF protocol message, and L group identifiers are located in a command node domain of an RPC layer of the third NETCONF protocol message. The public configuration data is the configuration data shared by the L groups of downstream devices indicated by the L group identifications.
With the method of the first aspect, since the public configuration data is the configuration data shared by the L groups of downstream devices indicated by the L group identifiers, in a scenario where the NETCONF management device issues the same configuration data to a specific L group device, the NETCONF management device may reduce the number of interactions between the NETCONF management device and the NETCONF proxy device to the greatest extent, reduce the occupation of data bandwidth, and improve the configuration efficiency by sending the third NETCONF protocol packet.
A second aspect of the present application provides another method for configuring a packet transmission, including:
the method comprises the steps that a network configuration NETCONF proxy device receives a first NETCONF protocol message which is sent by a NETCONF management device and comprises public configuration data and N pieces of grouping configuration data when the NETCONF proxy device is determined to have grouping capability; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data; the grouping capability is the capability of processing NETCONF protocol messages comprising public configuration data and grouping configuration data;
the NETCONF proxy device obtains a first packet identifier of first packet configuration data in the N pieces of packet configuration data, determines a first group of downstream devices corresponding to the first packet identifier, and configures the first packet configuration data and the public configuration data for the first group of downstream devices.
In the method, after receiving a first NETCONF protocol message including common configuration data and N packet configuration data, the NETCONF proxy device may determine, according to a first packet identifier of the first group of downstream devices, first packet configuration data corresponding to the first group of downstream devices, and configure the first group of downstream devices in combination with the common configuration data, thereby improving configuration efficiency of configuring the downstream devices.
Optionally, before the NETCONF proxy device obtains the first packet identifier of the first packet configuration data in the N packet configuration data, the method of the second aspect further includes:
the NETCONF proxy equipment analyzes the first NETCONF protocol message and acquires public configuration data and the N pieces of grouping configuration data in the first NETCONF protocol message;
for each packet configuration data in the N packet configuration data, the NETCONF proxy device determines at least one packet identifier included in the packet configuration data, and stores the packet configuration data in a packet storage area corresponding to each packet identifier in the at least one packet identifier, respectively;
the NETCONF proxy equipment stores the public configuration data into a public storage area;
said configuring said first group of downstream devices with said first packet configuration data and said common configuration data comprises:
the NETCONF proxy equipment reads first packet configuration data from a packet storage area corresponding to the first packet identifier and reads the public configuration data from the public storage area;
the NETCONF proxy device configures the first configuration data and the common configuration data for the first set of downstream devices.
In the method of the second aspect, the NETCONF proxy device stores the packet configuration data corresponding to each group of downstream devices into the packet storage area corresponding to the packet identifier corresponding to the group of downstream devices, and stores the common configuration data into the common storage area, thereby saving storage space and improving storage efficiency.
Optionally, the public configuration data and the N pieces of packet configuration data are located in a configuration data node domain in a content layer of the first NETCONF protocol packet.
A third aspect of the present application provides a device for configuring a packet, including:
a determining unit configured to determine whether the first NETCONF proxy device supports a packet capability; the grouping capability is the capability of processing a NETCONF protocol message comprising public configuration data and grouping configuration data;
a message generating unit, configured to generate a first NETCONF protocol message including public configuration data and N pieces of packet configuration data when the determining unit determines that the first NETCONF proxy device supports the packet capability; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data;
and the sending unit is used for sending the first NETCONF protocol message to the first NETCONF proxy equipment.
According to the apparatus provided in the third aspect of the present application, after determining that the first NETCONF proxy device supports the packet capability, the first NETCONF protocol message sent to the first NETCONF proxy device includes the public configuration data and N packet configuration data. Since each group configuration data includes at least one group identification, the group configuration data is used for indicating the group configuration data to be configuration data which is exclusively shared by at least one group of downstream devices indicated by the at least one group identification; the common configuration data is configuration data shared by all groups of downstream devices indicated by all the group identifiers in the N group configuration data, and therefore, the configuration data of each group of downstream devices is composed of the common configuration data and all the group configuration data including the group identifiers of the group of downstream devices, so that different configuration data of different downstream devices are sent to the first NETCONF proxy device through the same first NETCONF protocol message, interaction times when the downstream devices managed by the first NETCONF proxy device are configured are reduced, and efficiency of configuring and managing network devices is improved.
Optionally, the message generating unit is further configured to generate K second NETCONF protocol messages when the determining unit determines that the second NETCONF proxy device does not support the packet capability; each second NETCONF protocol message comprises independent configuration data and a group identifier or an equipment identifier corresponding to the independent configuration data; the independent configuration data is configuration data which is exclusively shared by a group of downstream devices indicated by the group identification or configuration data which is exclusively shared by the downstream devices indicated by the device identification;
the sending unit is configured to send the K second NETCONF protocol messages to the second NETCONF proxy device.
According to the apparatus provided in the third aspect of the present application, when it is determined that the second NETCONF proxy device does not support the packet capability, K second NETCONF protocol messages are generated and sent. The second NETCONF protocol message is in the format of the NETCONF protocol message in the prior art, so that the second NETCONF protocol message can interact with second NETCONF proxy equipment which does not support grouping capability, and the equipment compatibility is improved.
Optionally, the public configuration data and the N pieces of packet configuration data are located in a configuration data node domain in a content layer of the first NETCONF protocol packet.
A fourth aspect of the present application provides another configuration packet sending apparatus, including:
the network configuration proxy equipment comprises a receiving unit, a sending unit and a receiving unit, wherein the receiving unit is used for receiving a first network configuration protocol message which is sent by network configuration management equipment and comprises public configuration data and N pieces of grouping configuration data when determining that the network configuration proxy equipment has grouping capability; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data; the grouping capability is the capability of processing NETCONF protocol messages comprising public configuration data and grouping configuration data;
a configuration unit, configured to obtain a first packet identifier of a first packet configuration data in the N packet configuration data, determine a first group of downstream devices corresponding to the first packet identifier, and configure the first packet configuration data and the common configuration data for the first group of downstream devices.
Optionally, the apparatus of the fourth aspect further comprises a processing unit, configured to: analyzing the first NETCONF protocol message to obtain public configuration data and the N pieces of grouping configuration data in the first NETCONF protocol message; for each group configuration data in the N group configuration data, determining at least one group identifier included in the group configuration data, respectively storing the group configuration data in a group storage area corresponding to each group identifier in the at least one group identifier, and storing the common configuration data in a common storage area;
a storage unit for storing the N pieces of grouping configuration data and the common configuration data;
the configuration unit is specifically configured to read first packet configuration data from a packet storage area corresponding to the first packet identifier, read the common configuration data from the common storage area, and configure the first packet configuration data and the common configuration data for the first group of downstream devices.
According to the apparatus provided in the fourth aspect of the present application, after receiving the first NETCONF protocol packet including the common configuration data and the N packet configuration data, the first packet configuration data corresponding to the first group of downstream devices may be determined according to the first packet identifier of the first group of downstream devices, and the first group of downstream devices may be configured in combination with the common configuration data, thereby improving the configuration efficiency for configuring the downstream devices.
Optionally, the public configuration data and the N pieces of packet configuration data are located in a configuration data node domain in a content layer of the first NETCONF protocol packet.
A fifth aspect of the present application provides another configuration packet sending apparatus, including:
a processor to determine whether the first NETCONF proxy device supports packet capabilities; the grouping capability is the capability of processing a NETCONF protocol message comprising public configuration data and grouping configuration data;
the processor is used for generating a first NETCONF protocol message comprising public configuration data and N pieces of grouping configuration data when the fact that the first NETCONF proxy equipment supports the grouping capability is determined; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data;
a transceiver, configured to send the first NETCONF protocol packet to the first NETCONF proxy device.
According to the apparatus provided in the fifth aspect of the present application, after determining that the first NETCONF proxy device supports the packet capability, the first NETCONF protocol message sent to the first NETCONF proxy device includes the public configuration data and N packet configuration data. Since each group configuration data includes at least one group identification, the group configuration data is used for indicating the group configuration data to be configuration data which is exclusively shared by at least one group of downstream devices indicated by the at least one group identification; the common configuration data is configuration data shared by all groups of downstream devices indicated by all the group identifiers in the N group configuration data, and therefore, the configuration data of each group of downstream devices is composed of the common configuration data and all the group configuration data including the group identifiers of the group of downstream devices, so that different configuration data of different downstream devices are sent to the first NETCONF proxy device through the same first NETCONF protocol message, interaction times when the NETCONF management device configures the downstream devices managed by the first NETCONF proxy device are reduced, and efficiency of configuring and managing network devices is improved.
Optionally, the processor is further configured to generate K second NETCONF protocol packets when it is determined that the second NETCONF proxy device does not support the packet capability; each second NETCONF protocol message comprises independent configuration data and a group identifier or an equipment identifier corresponding to the independent configuration data; the independent configuration data is configuration data which is exclusively shared by a group of downstream devices indicated by the group identification or configuration data which is exclusively shared by the downstream devices indicated by the device identification;
the transceiver is configured to send the K second NETCONF protocol messages to the second NETCONF proxy device.
According to the apparatus provided in the fifth aspect of the present application, when it is determined that the second NETCONF proxy device does not support the packet capability, K second NETCONF protocol messages are generated and sent. The second NETCONF protocol message is in the format of the NETCONF protocol message in the prior art, so that the second NETCONF protocol message can interact with second NETCONF proxy equipment which does not support grouping capability, and the equipment compatibility is improved.
Optionally, the public configuration data and the N pieces of packet configuration data are located in a configuration data node domain in a content layer of the first NETCONF protocol packet.
A sixth aspect of the present application provides yet another configuration packet sending apparatus, including:
the network configuration proxy equipment comprises a transceiver and a server, wherein the transceiver is used for receiving a first network configuration protocol message which is sent by network configuration management equipment and comprises public configuration data and N pieces of grouping configuration data when determining that the network configuration proxy equipment has grouping capability; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data; the grouping capability is the capability of processing NETCONF protocol messages comprising public configuration data and grouping configuration data;
the processor is configured to obtain a first packet identifier of first packet configuration data in the N packet configuration data, determine a first group of downstream devices corresponding to the first packet identifier, and configure the first packet configuration data and the common configuration data for the first group of downstream devices.
According to the apparatus provided in the sixth aspect of the present application, after receiving the first NETCONF protocol packet including the common configuration data and the N packet configuration data, the first packet configuration data corresponding to the first group of downstream devices may be determined according to the first packet identifier of the first group of downstream devices, and the first group of downstream devices may be configured by combining the common configuration data, so that the configuration efficiency of configuring the downstream devices is improved.
Optionally, the apparatus further comprises a memory;
the processor is specifically configured to: analyzing the first NETCONF protocol message to obtain public configuration data and the N pieces of grouping configuration data in the first NETCONF protocol message; for each group configuration data in the N group configuration data, determining at least one group identifier included in the group configuration data, respectively storing the group configuration data in a group storage area corresponding to each group identifier in the at least one group identifier, and storing the common configuration data in a common storage area;
the memory for storing the N grouped configuration data and the common configuration data;
the processor is specifically configured to read first packet configuration data from a packet storage area corresponding to the first packet identifier, read the common configuration data from the common storage area, and configure the first packet configuration data and the common configuration data for the first group of downstream devices.
According to the apparatus provided in the sixth aspect of the present application, the NETCONF proxy device stores the packet configuration data corresponding to each group of downstream devices in the packet storage area corresponding to the packet identifier corresponding to the group of downstream devices, and stores the common configuration data in the common storage area, thereby saving storage space and improving storage efficiency.
Optionally, the public configuration data and the N pieces of packet configuration data are located in a configuration data node domain in a content layer of the first NETCONF protocol packet.
Drawings
Fig. 1 is a schematic diagram of a typical NETCONF application scenario;
fig. 2 is a schematic flow chart of a configuration packet sending method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a configuration packet sending apparatus according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a configuration packet sending apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a configuration packet sending apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a configuration packet sending apparatus according to an embodiment of the present application.
Detailed Description
The NETCONF protocol is divided into four layers: a content layer, an operation layer, a remote procedure Call Protocol (PRC) layer, and an application Protocol layer. The content layer describes configuration data configured by the NETCONF management device. The operation layer defines a set of basic primitive operations that are applied in RPC and which will constitute the basic capabilities of NETCONF. The RPC layer provides a simple, transport protocol independent mechanism for the encoding of the RPC module. The application protocol layer is used to provide a secure data bearer channel.
Three network elements may be involved in the NETCONF protocol: NETCONF management equipment, NETCONF proxy equipment and downstream equipment managed by the NETCONF proxy equipment. The NETCONF management device is equivalent to a client (client), and the configuration of downstream equipment managed by the NETCONF proxy device is realized by sending a configuration message to the NETCONF proxy device. The NETCONF proxy device is equivalent to a server (server), and can analyze the configuration message and configure and manage the downstream device managed by the NETCONF proxy device according to the configuration data in the configuration message. The downstream device may or may not support the NETCONF protocol. If the downstream device does not support the NETCONF protocol, the NETCONF proxy device needs to repackage the configuration data into a message of a protocol supported by other downstream devices, And send the message to the downstream device, for example, a Control And configuration protocol (CAPWAP) message of a Wireless Access point. In a wireless access scenario, the NETCONF management device may be a centralized controller, the NETCONF agent device may be an Access Controller (AC), and the downstream device may be an Access Point (AP).
When the NETCONF proxy device manages a plurality of downstream devices, the plurality of downstream devices may be divided into a plurality of groups, and the configuration data required by the downstream devices in each group may be the same. At present, NETCONF management equipment needs to issue configuration data of each group of downstream equipment or each downstream equipment one by one, and the efficiency is low. In order to solve the above problem, an embodiment of the present application provides a method for sending a configuration packet, which is described in detail below.
As shown in fig. 2, a schematic flow chart of a configuration packet sending method provided in the embodiment of the present application includes:
step 201: the NETCONF management device determines that the first NETCONF agent device supports grouping capability; the packet capability is a capability of processing a NETCONF protocol message including common configuration data and packet configuration data.
Step 202: the NETCONF management equipment generates a first NETCONF protocol message comprising public configuration data and N pieces of grouping configuration data; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream devices indicated by all group identifications in the N group configuration data.
Step 203: and the NETCONF management equipment sends the first NETCONF protocol message to the first NETCONF agent equipment.
Step 204: the method comprises the steps that a first NETCONF proxy device receives a first NETCONF protocol message which is sent by a NETCONF management device and contains public configuration data and N pieces of grouping configuration data when the NETCONF proxy device is determined to have grouping capability.
Step 205: the first NETCONF proxy device obtains a first packet identifier of first packet configuration data in the N pieces of packet configuration data, determines a first group of downstream devices corresponding to the first packet identifier, and configures the first packet configuration data and the public configuration data for the first group of downstream devices.
Before step 201, the NETCONF management device may initiate a connection request to the first NETCONF proxy device, and the first NETCONF proxy device completes the establishment of a connection with the NETCONF management device after passing the identity authentication of the NETCONF management device.
After the connection between the NETCONF management device and the first NETCONF agent device is established, the NETCONF management device and the first NETCONF agent device need to perform capability set exchange, so that the NETCONF management device and the first NETCONF agent device mutually determine the capabilities supported by the other party. Wherein a capability set refers to the set of all capabilities supported by a device.
At present, according to the NETCONF protocol, the NETCONF management device and the first NETCONF proxy device complete capability set exchange by sending hello messages to each other. Specifically, after the connection between the NETCONF management device and the first NETCONF proxy device is established, the NETCONF management device sends a hello message including a capability set supported by the NETCONF management device to the first NETCONF proxy device, where the hello message includes the capability set supported by the NETCONF management device; meanwhile, the first NETCONF proxy device also sends a hello message including the capability set supported by the first NETCONF proxy device to the NETCONF management device. At this time, the NETCONF management device completes capability set exchange with the first NETCONF proxy device.
For example, the contents in the hello message sent by the NETCONF management device may be as follows:
<hello xmlns＝"urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>
<capability>urn:ietf:params:netconf:base:1.1</capability>
<capability>urn:ietf:params:netconf:capability:group:1.0</capab ility>
</capabilities>
<session-id>4</session-id>
</hello>
in the hello message, "urn: ietf: params: NETCONF: base: 1.1" indicates that the NETCONF management device supports the basic capability set specified in the NETCONF protocol, and the version of the supported basic capability set is V1.1; "urn: ietf: params: NETCONF: capability: group: 1.0" indicates that the NETCONF management device supports the grouping capability, and the version of the grouping capability is V1.0.
Of course, the above is only an example, and the hello packet may also have other forms, which are determined according to the actual situation, and are not described herein again.
In step 201, after the network configuration management device completes capability set exchange with the first network configuration proxy device, the network configuration management device may determine all the capabilities supported by the first network configuration proxy device, so as to determine whether the first network configuration proxy device supports the packet capability.
In this embodiment, the packet capability may be a capability of processing a NETCONF protocol packet including common configuration data and packet configuration data. Specifically, the device with grouping capability may generate a NETCONF protocol packet including public configuration data and grouping configuration data; the capabilities of NETCONF protocol messages including public configuration data and packet configuration data can be parsed.
In the embodiment of the present application, the configuration data may be data for configuring a Domain Name Server (DNS), or data for configuring a Dynamic Host Configuration Protocol (DHCP).
After the capability set exchange is completed between the NETCONF management device and the first NETCONF proxy device, the NETCONF management device may also group a plurality of downstream devices managed by the first NETCONF proxy device. In a possible implementation manner, the first NETCONF agent device sends device information such as a device identifier of each downstream device managed by the first NETCONF agent device to the NETCONF management device, and the NETCONF management device groups the downstream devices managed by the first NETCONF agent device according to the received device information reported by the first NETCONF agent device, and sends the group information to the first NETCONF agent device.
In another possible implementation manner, the NETCONF management device issues a grouping policy to the first NETCONF proxy device according to the received device information reported by the first NETCONF proxy device, and the first NETCONF proxy device thereby groups the plurality of downstream devices managed by the first NETCONF proxy device according to the received grouping policy. And finally, the first NETCONF agent equipment reports the grouped grouping information to the NETCONF management equipment.
It should be noted that, in the embodiment of the present application, one downstream device may belong to a plurality of different groups, and specifically, the group to which each downstream device belongs may be determined according to an actual situation.
In the embodiment of the application, the grouping information can be transmitted through the message in the NETCONF format; packet information may also be transmitted via messages of other formats. Before transmitting packet information through a message in NETCONF format, the format of the message needs to be defined in advance through a Next Generation (YANG) model.
Optionally, in this embodiment of the present application, the format of the message defined by the YANG model may be the following format:
Figure BDA0000946275630000141
in combination with the above YANG model, the messages that divide the three downstream devices with device identifiers a, b, and c into the group with group identifier 1 can be represented as follows:
Figure BDA0000946275630000142
Figure BDA0000946275630000151
in step 202, the first NETCONF protocol message generated by the NETCONF management device generally includes an RPC layer, an operation layer, and a content layer. As described above, the content layer describes configuration data configured by the NETCONF management device for the downstream device managed by the first NETCONF proxy device, and for this reason, in this embodiment of the present application, the common configuration data and the N pieces of packet configuration data are located in the configuration data node domain in the content layer of the first NETCONF protocol packet. Wherein N is a natural number.
In this embodiment of the present application, each packet configuration data in the first NETCONF protocol message includes at least one packet identifier, so as to indicate a downstream device to which each packet configuration data corresponds.
For example, the first NETCONF protocol message includes two packet configuration data, which are as follows:
<vlan group＝“1，2”>1111</vlan>
<vlan group＝“3”>333</vlan>
in the above packet configuration data, < vlan group ═ 1, 2 "> 1111</vlan > is packet configuration data for a group of downstream devices indicated by the packet identifier 1 and a group of downstream devices indicated by the packet identifier 2, and is used to configure a vlan (Virtual Local Area Network) of the group of downstream devices indicated by the packet identifier 1 and the group of downstream devices indicated by the packet identifier 2 to 1111. And the < vlan group ═ 3 "> 333</vlan > is packet configuration data for a set of downstream devices indicated by the packet identification 3, for configuring the vlan of the set of downstream devices indicated by the packet identification 3 as 333.
By the method, the NETCONF management equipment can configure data for different groups of downstream equipment through a first NETCONF protocol message.
It should be noted that, in this embodiment of the application, if the NETCONF management device also manages a second NETCONF proxy device that does not support the packet capability, the method in the prior art may be used to perform configuration data on the downstream device managed by the second NETCONF proxy device. Specifically, the NETCONF management device may generate K second NETCONF protocol messages; each second NETCONF protocol message comprises independent configuration data and a group identifier or an equipment identifier corresponding to the independent configuration data; the independent configuration data is configuration data which is exclusively shared by a group of downstream devices indicated by the group identification or configuration data which is exclusively shared by the downstream devices indicated by the device identification; and the NETCONF management equipment sends the K second NETCONF protocol messages to the second NETCONF agent equipment. Wherein K is a positive integer greater than 1.
Certainly, the configuration data of the downstream device managed by the second NETCONF proxy device may also be implemented by other methods, which is not described herein again.
In step 203, if it is determined that the first NETCONF proxy device supports the packet capability, the NETCONF management device may further generate a third NETCONF protocol packet for transmitting configuration data shared by L groups of downstream devices indicated by the L packet identifiers. Specifically, if determining that a first NETCONF proxy device supports the packet capability, the NETCONF management device sends a third NETCONF protocol message including public configuration data and L packet identifiers to the first NETCONF proxy device; wherein, L is a natural number, the public configuration data is located in a configuration data node domain of a content layer of the third NETCONF protocol message, and L group identifiers are located in a command node domain of an RPC layer of the third NETCONF protocol message. The public configuration data is the configuration data shared by the L groups of downstream devices indicated by the L group identifications.
By the method, the public configuration data is the configuration data shared by the L groups of downstream devices indicated by the L groups of grouping identifiers, and the NETCONF management device can reduce the interaction times between the NETCONF management device and the NETCONF proxy device to the greatest extent, reduce the occupation of data bandwidth and improve the configuration efficiency by sending the third NETCONF protocol message under the scene that the NETCONF management device issues the same configuration data to the specific L groups of grouping devices.
In step 204, before the first NETCONF proxy device receives the first NETCONF protocol packet, it may also perform capability set exchange with the NETCONF management device. For the specific steps of exchanging the capability sets between the first NETCONF agent device and the NETCONF management device, reference may be made to the foregoing description, and details are not described herein again.
In step 205, after receiving the first NETCONF protocol packet, the first NETCONF proxy device parses the first NETCONF protocol packet, thereby obtaining the public configuration data and the N packet configuration data in the first NETCONF protocol packet.
After the first NETCONF proxy device obtains the N packet configuration data, it may determine the first packet configuration data, thereby determining the first packet identifier in the first packet configuration data. The first group configuration data may be any group configuration data in the N group configuration data, and the first group identifier is at least one group identifier included in the first group configuration data.
In this embodiment of the application, the first NETCONF proxy device may store the common configuration data in a common storage area, and store each packet configuration data in at least one packet storage area corresponding to at least one packet identifier included in the packet configuration data. For example, if the packet configuration data includes two packet identifiers, which are a and B, the packet configuration data is stored in the packet storage area corresponding to a and the packet storage area corresponding to B, respectively.
By the method, the configuration data shared by all the groups of downstream equipment is stored in the public storage area, and meanwhile, the configuration data shared by each group of downstream equipment is reserved with low cost, so that the storage space is effectively saved, and the storage efficiency is improved.
It should be noted that, the first NETCONF proxy device may store the group configuration data or the common configuration data in an xml format, or store the group configuration data or the common configuration data in a key-value database, which is not limited in this embodiment of the present invention.
When the first NETCONF proxy device configures a first group of downstream device configurations, a first group identifier is determined according to the first group of downstream device configurations, first group configuration data is read from a group storage area corresponding to the first group identifier, and the common configuration data is read from the common storage area, so that all configuration data corresponding to the first group of downstream device configurations are obtained. And then, the first NETCONF proxy device configures the read first group of configuration data and the public configuration data to the first group of downstream devices, so as to realize the configuration of the first group of downstream devices.
In this embodiment of the present application, the first NETCONF proxy device may also receive a third NETCONF protocol packet sent by the NETCONF management device. Specifically, a first NETCONF proxy device receives a third NETCONF protocol message which is sent by a NETCONF management device after the first NETCONF proxy device is determined to support the grouping capability and comprises public configuration data and L grouping identifiers; wherein, L is a natural number, the public configuration data is located in a configuration data node domain of a content layer of the third NETCONF protocol message, and L group identifiers are located in a command node domain of an RPC layer of the third NETCONF protocol message. The public configuration data is the configuration data shared by the L groups of downstream devices indicated by the L group identifications.
The first NETCONF proxy device may configure, according to public configuration data in the third NETCONF protocol message, the L groups of downstream devices indicated by the L packet identifiers, thereby improving configuration efficiency.
Optionally, the first NETCONF proxy device may further store the public configuration data in a public storage area corresponding to the L groups of downstream devices indicated by the L group identifiers, so as to save a storage space and improve storage efficiency.
Based on the same technical concept, the embodiment of the present application further provides a device for sending configuration messages, and the device can execute the method embodiment.
As shown in fig. 3, a schematic structural diagram of a configuration message sending apparatus is provided for the embodiment of the present application.
The apparatus may perform the process shown in fig. 2, and includes:
a determining unit 301 for determining whether the first NETCONF proxy device supports the packet capability; the grouping capability is the capability of processing a NETCONF protocol message comprising public configuration data and grouping configuration data;
a message generating unit 302, configured to generate a first NETCONF protocol message including public configuration data and N pieces of packet configuration data when the determining unit determines that the first NETCONF proxy device supports the packet capability; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data;
a sending unit 303, configured to send the first NETCONF protocol packet to the first NETCONF proxy device.
Optionally, the message generating unit 302 is further configured to generate K second NETCONF protocol messages when the determining unit 301 determines that the second NETCONF proxy device does not support the packet capability; each second NETCONF protocol message comprises independent configuration data and a group identifier or an equipment identifier corresponding to the independent configuration data; the independent configuration data is configuration data which is exclusively shared by a group of downstream devices indicated by the group identification or configuration data which is exclusively shared by the downstream devices indicated by the device identification;
the sending unit 303 is configured to send the K second NETCONF protocol messages to the second NETCONF proxy device.
Optionally, the public configuration data and the N pieces of packet configuration data are located in a configuration data node domain in a content layer of the first NETCONF protocol packet.
As shown in fig. 4, a schematic structural diagram of a configuration message sending apparatus is provided for the embodiment of the present application.
Referring to fig. 4, the apparatus includes:
a receiving unit 401, configured to receive a first NETCONF protocol packet that includes public configuration data and N pieces of packet configuration data and is sent by a NETCONF management device when determining that the NETCONF proxy device has a packet capability; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data; the grouping capability is the capability of processing NETCONF protocol messages comprising public configuration data and grouping configuration data;
a configuring unit 402, configured to obtain a first packet identifier of a first packet configuration data in the N packet configuration data, determine a first group of downstream devices corresponding to the first packet identifier, and configure the first packet configuration data and the common configuration data for the first group of downstream devices.
Optionally, the apparatus further includes a processing unit 403, configured to: analyzing the first NETCONF protocol message to obtain public configuration data and the N pieces of grouping configuration data in the first NETCONF protocol message; for each group configuration data in the N group configuration data, determining at least one group identifier included in the group configuration data, respectively storing the group configuration data in a group storage area corresponding to each group identifier in the at least one group identifier, and storing the common configuration data in a common storage area;
a storage unit 404, configured to store the N grouping configuration data and the common configuration data;
the configuration unit 402 is specifically configured to read first packet configuration data from a packet storage area corresponding to the first packet identifier, read the common configuration data from the common storage area, and configure the first packet configuration data and the common configuration data for the first group of downstream devices.
Optionally, the public configuration data and the N pieces of packet configuration data are located in a configuration data node domain in a content layer of the first NETCONF protocol packet.
As shown in fig. 5, a schematic structural diagram of a configuration message sending apparatus is provided for the embodiment of the present application.
Referring to fig. 5, the apparatus includes: a processor 501, a memory 502, and a transceiver 503.
The transceiver 503 may be a wired transceiver, a wireless transceiver, or a combination thereof. The wired transceiver may be, for example, an ethernet interface. The ethernet interface may be an optical interface, an electrical interface, or a combination thereof. The wireless transceiver may be, for example, a wireless local area network communication interface, a cellular network communication interface, or a combination thereof. The processor 501 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of CPU and NP. The processor 501 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof. The memory 502 may include a volatile memory (RAM), such as a random-access memory (RAM); the memory 502 may also include a non-volatile memory (ROM), such as a read-only memory (ROM), a flash memory (flash memory), a Hard Disk Drive (HDD), or a solid-state drive (SSD); the memory 502 may also comprise a combination of memories of the kind described above.
The memory 502 may be used to store programs.
The processor 501 reads the instructions corresponding to the program from the memory 502, and performs the following operations:
determining whether the first NETCONF proxy device supports packet capabilities; the grouping capability is the capability of processing a NETCONF protocol message comprising public configuration data and grouping configuration data; when determining that the first NETCONF proxy equipment supports the grouping capability, generating a first NETCONF protocol message comprising public configuration data and N pieces of grouping configuration data; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data;
a transceiver 503, configured to send the first NETCONF protocol packet to the first NETCONF proxy device.
Optionally, the processor 501 is further configured to generate K second NETCONF protocol packets when it is determined that the second NETCONF proxy device does not support the packet capability; each second NETCONF protocol message comprises independent configuration data and a group identifier or an equipment identifier corresponding to the independent configuration data; the independent configuration data is configuration data which is exclusively shared by a group of downstream devices indicated by the group identification or configuration data which is exclusively shared by the downstream devices indicated by the device identification;
the transceiver 503 is configured to send the K second NETCONF protocol messages to the second NETCONF proxy device.
Optionally, the public configuration data and the N pieces of packet configuration data are located in a configuration data node domain in a content layer of the first NETCONF protocol packet.
A bus may also be included in fig. 5, which may include any number of interconnected buses and bridges, with various circuits of one or more processors, represented by a processor, and memory, represented by a memory, linked together. The bus may also link various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are not described in any further detail herein. The transceiver provides a means for communicating with various other apparatus over a transmission medium. The processor is responsible for managing the bus architecture and the usual processing, and the memory may store data used by the processor in performing operations.
As shown in fig. 6, a schematic structural diagram of a configuration message sending apparatus is provided for the embodiment of the present application.
Referring to fig. 6, the apparatus includes: a processor 601, a memory 602, a transceiver 603.
The transceiver 603 may be a wired transceiver, a wireless transceiver, or a combination thereof. The wired transceiver may be, for example, an ethernet interface. The ethernet interface may be an optical interface, an electrical interface, or a combination thereof. The wireless transceiver may be, for example, a wireless local area network communication interface, a cellular network communication interface, or a combination thereof. The processor 601 may be a central processing unit, a network processor, or a combination of a CPU and an NP. The processor 601 may further include a hardware chip. The hardware chip may be an application specific integrated circuit, a programmable logic device, or a combination thereof. The PLD may be a complex programmable logic device, a field programmable gate array, general purpose array logic, or any combination thereof. The memory 602 may include volatile memory, such as random access memory; the memory 602 may also include non-volatile memory, such as read-only memory, flash memory, a hard disk, or a solid state disk; the memory 602 may also comprise a combination of memories of the kind described above.
The memory 602 may be used to store programs.
The network configuration proxy equipment comprises a transceiver and a server, wherein the transceiver is used for receiving a first network configuration protocol message which is sent by network configuration management equipment and comprises public configuration data and N pieces of grouping configuration data when determining that the network configuration proxy equipment has grouping capability; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data; the grouping capability is the capability of processing NETCONF protocol messages comprising public configuration data and grouping configuration data;
the processor 601 reads the instructions corresponding to the program from the memory 602, and performs the following operations:
the method is used for acquiring a first packet identifier of first packet configuration data in the N pieces of packet configuration data, determining a first group of downstream devices corresponding to the first packet identifier, and configuring the first packet configuration data and the common configuration data for the first group of downstream devices.
Optionally, the processor 601 is specifically configured to: analyzing the first NETCONF protocol message to obtain public configuration data and the N pieces of grouping configuration data in the first NETCONF protocol message; for each group configuration data in the N group configuration data, determining at least one group identifier included in the group configuration data, respectively storing the group configuration data in a group storage area corresponding to each group identifier in the at least one group identifier, and storing the common configuration data in a common storage area;
the memory 602 is configured to store the N grouped configuration data and the common configuration data;
the processor 601 is specifically configured to read first packet configuration data from a packet storage area corresponding to the first packet identifier, read the common configuration data from the common storage area, and configure the first packet configuration data and the common configuration data for the first group of downstream devices.
Optionally, the public configuration data and the N pieces of packet configuration data are located in a configuration data node domain in a content layer of the first NETCONF protocol packet.
A bus may also be included in fig. 6, which may include any number of interconnected buses and bridges, with various circuits of one or more processors, represented by a processor, and memory, represented by a memory, linked together. The bus may also link various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are not described in any further detail herein. The transceiver provides a means for communicating with various other apparatus over a transmission medium. The processor is responsible for managing the bus architecture and the usual processing, and the memory may store data used by the processor in performing operations.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the scope of the application. Thus, to the extent that such modifications and variations of the present application fall within the scope of the claims of the present application, it is intended that the present application also encompass such modifications and variations.

Claims (12)

1. A method for sending configuration messages is characterized in that the method comprises the following steps:
the network configuration NETCONF management equipment determines that the first NETCONF agent equipment supports grouping capability; the grouping capability is the capability of processing a NETCONF protocol message comprising public configuration data and grouping configuration data;
the NETCONF management equipment generates a first NETCONF protocol message comprising public configuration data and N pieces of grouping configuration data; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data;
and the NETCONF management equipment sends the first NETCONF protocol message to the first NETCONF agent equipment.
2. The method of claim 1, wherein the method further comprises:
the NETCONF management equipment determines that second NETCONF agent equipment does not support grouping capability, and then K second NETCONF protocol messages are generated; each second NETCONF protocol message comprises independent configuration data and a group identifier or an equipment identifier corresponding to the independent configuration data; the independent configuration data is configuration data which is exclusively shared by a group of downstream devices indicated by the group identification or configuration data which is exclusively shared by the downstream devices indicated by the device identification;
and the NETCONF management equipment sends the K second NETCONF protocol messages to the second NETCONF agent equipment.
3. The method of claim 1, wherein the common configuration data and the N packet configuration data are located in a configuration data node field in a content layer of the first NETCONF protocol packet.
4. A method for sending configuration messages is characterized in that the method comprises the following steps:
the method comprises the steps that a network configuration NETCONF proxy device receives a first NETCONF protocol message which is sent by a NETCONF management device and comprises public configuration data and N pieces of grouping configuration data when the NETCONF proxy device is determined to have grouping capability; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data; the grouping capability is the capability of processing NETCONF protocol messages comprising public configuration data and grouping configuration data;
the NETCONF proxy device obtains a first packet identifier of first packet configuration data in the N pieces of packet configuration data, determines a first group of downstream devices corresponding to the first packet identifier, and configures the first packet configuration data and the public configuration data for the first group of downstream devices.
5. The method of claim 4, wherein before the NETCONF proxy device obtains the first packet identification of the first packet configuration data of the N packet configuration data, the method further comprises:
the NETCONF proxy equipment analyzes the first NETCONF protocol message and acquires public configuration data and the N pieces of grouping configuration data in the first NETCONF protocol message;
for each packet configuration data in the N packet configuration data, the NETCONF proxy device determines at least one packet identifier included in the packet configuration data, and stores the packet configuration data in a packet storage area corresponding to each packet identifier in the at least one packet identifier, respectively;
the NETCONF proxy equipment stores the public configuration data into a public storage area;
said configuring said first group of downstream devices with said first packet configuration data and said common configuration data comprises:
the NETCONF proxy equipment reads first packet configuration data from a packet storage area corresponding to the first packet identifier and reads the public configuration data from the public storage area;
the NETCONF proxy device configures the first configuration data and the common configuration data for the first set of downstream devices.
6. A method according to claim 4 or 5, characterized in that the common configuration data and the N packet configuration data are located in a configuration data node field in the content layer of the first NETCONF protocol packet.
7. A configuration message transmission apparatus, comprising:
a determining unit configured to determine whether the first NETCONF proxy device supports a packet capability; the grouping capability is the capability of processing a NETCONF protocol message comprising public configuration data and grouping configuration data;
a message generating unit, configured to generate a first NETCONF protocol message including public configuration data and N pieces of packet configuration data when the determining unit determines that the first NETCONF proxy device supports the packet capability; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data;
and the sending unit is used for sending the first NETCONF protocol message to the first NETCONF proxy equipment.
8. The apparatus according to claim 7, wherein the message generating unit is further configured to generate K second NETCONF protocol messages when the determining unit determines that the second NETCONF proxy device does not support the packet capability; each second NETCONF protocol message comprises independent configuration data and a group identifier or an equipment identifier corresponding to the independent configuration data; the independent configuration data is configuration data which is exclusively shared by a group of downstream devices indicated by the group identification or configuration data which is exclusively shared by the downstream devices indicated by the device identification;
the sending unit is configured to send the K second NETCONF protocol messages to the second NETCONF proxy device.
9. The apparatus of claim 7, wherein the common configuration data and the N packet configuration data are located in a configuration data node field in a content layer of the first NETCONF protocol packet.
10. A configuration message transmission apparatus, comprising:
the device comprises a receiving unit, a sending unit and a sending unit, wherein the receiving unit is used for receiving a first NETCONF protocol message which is sent by NETCONF management equipment and comprises public configuration data and N pieces of grouping configuration data when the grouping capability of the device is determined; each group configuration data comprises at least one group identifier for indicating that the group configuration data is configuration data which is exclusive to at least one group of downstream devices indicated by the at least one group identifier; the common configuration data is configuration data shared by all groups of downstream equipment indicated by all the group identifications in the N groups of configuration data; the grouping capability is the capability of processing NETCONF protocol messages comprising public configuration data and grouping configuration data;
a configuration unit, configured to obtain a first packet identifier of a first packet configuration data in the N packet configuration data, determine a first group of downstream devices corresponding to the first packet identifier, and configure the first packet configuration data and the common configuration data for the first group of downstream devices.
11. The apparatus of claim 10, wherein the apparatus further comprises a processing unit to: analyzing the first NETCONF protocol message to obtain public configuration data and the N pieces of grouping configuration data in the first NETCONF protocol message; for each group configuration data in the N group configuration data, determining at least one group identifier included in the group configuration data, respectively storing the group configuration data in a group storage area corresponding to each group identifier in the at least one group identifier, and storing the common configuration data in a common storage area;
a storage unit for storing the N pieces of grouping configuration data and the common configuration data;
the configuration unit is specifically configured to read first packet configuration data from a packet storage area corresponding to the first packet identifier, read the common configuration data from the common storage area, and configure the first packet configuration data and the common configuration data for the first group of downstream devices.
12. The apparatus of claim 10, wherein the common configuration data and the N packet configuration data are located in a configuration data node field in a content layer of the first NETCONF protocol packet.
CN201610164075.2A 2016-03-21 2016-03-21 Configuration message sending method and device Active CN107222321B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610164075.2A CN107222321B (en) 2016-03-21 2016-03-21 Configuration message sending method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610164075.2A CN107222321B (en) 2016-03-21 2016-03-21 Configuration message sending method and device

Publications (2)

Publication Number Publication Date
CN107222321A CN107222321A (en) 2017-09-29
CN107222321B true CN107222321B (en) 2020-08-14

Family

ID=59927255

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610164075.2A Active CN107222321B (en) 2016-03-21 2016-03-21 Configuration message sending method and device

Country Status (1)

Country Link
CN (1) CN107222321B (en)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110278093B (en) * 2018-03-13 2021-12-28 华为技术有限公司 Configuration method and device of network equipment
CN109194519B (en) * 2018-09-27 2021-11-16 锐捷网络股份有限公司 Configuration method and device of network equipment, controller and computer storage medium
CN109586961B (en) * 2018-11-28 2022-03-01 新华三技术有限公司 Network configuration method and device
CN112217845B (en) * 2019-07-09 2022-01-18 华为技术有限公司 Data transmission method based on Netconf protocol and related equipment
CN113064658B (en) * 2019-12-31 2023-09-08 北京华为数字技术有限公司 Copying method, copying device, copying equipment and computer readable storage medium for configuration data
CN113938403A (en) * 2020-07-13 2022-01-14 华为技术有限公司 Capability notification method and related equipment
WO2023168573A1 (en) * 2022-03-07 2023-09-14 Shenzhen Tcl New Technology Co., Ltd. Wireless communication method and device for extended reality traffic

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1885858A (en) * 2005-06-24 2006-12-27 中国长城计算机深圳股份有限公司 Method for carrying out cluster management on network equipment based on SNMP protocol
CN101110822B (en) * 2007-07-06 2011-11-02 华为技术有限公司 Event notice sending method, system and equipment based on network configuration protocol
CN101183977A (en) * 2007-10-26 2008-05-21 杭州华三通信技术有限公司 Configuration distributing method and apparatus
CN101237466B (en) * 2008-02-29 2012-09-05 华为技术有限公司 Network configuration method, device and system for terminal
CN101399774B (en) * 2008-10-24 2012-07-04 华为技术有限公司 Processing method and system for packet data
US8798002B2 (en) * 2010-09-30 2014-08-05 Htc Corporation Method of sending network configuration and related communication device
US8730965B2 (en) * 2011-01-05 2014-05-20 Google Inc. Systems and methods for dynamic routing in a multiprocessor network using local congestion sensing
EP2509261B1 (en) * 2011-04-08 2013-10-30 Alcatel Lucent Monitoring of a network element in a packet-switched network
CN102368716A (en) * 2011-11-29 2012-03-07 迈普通信技术股份有限公司 Data acquisition method of network configuration protocol and network configuration server

Also Published As

Publication number Publication date
CN107222321A (en) 2017-09-29

Similar Documents

Publication Publication Date Title
CN107222321B (en) Configuration message sending method and device
US11146462B2 (en) Network slice management method, device, and system
US11228947B2 (en) Network slice deployment method and related device
EP3836577B1 (en) Session management method and device for user groups
US11368904B2 (en) Network slice selection method and apparatus
WO2018058579A1 (en) Method for managing network slice and management unit
WO2018171459A1 (en) Network slice management method and device
EP3657861B1 (en) Deploying a network slice
EP3713372A1 (en) Method and device for creating user group
US20220060881A1 (en) Group management method, apparatus, and system
US11088924B2 (en) Network management method, device, and system
CN110875827B (en) Network slice management method and device
WO2018048769A1 (en) System and method for programmable native analytics in 5g mobile networks
WO2019029522A1 (en) Method for managing network component, and network device
WO2019047769A1 (en) Method, device and system for processing network slice instance
WO2019024671A1 (en) Method, device and system for deploying network slice
WO2019057015A1 (en) Network slice management method and apparatus
CN109391503B (en) Network slice management method and device
EP4319232A1 (en) Communication method and apparatus
US10129739B2 (en) Data transmission method and device
EP3032801A1 (en) Method and device for generating forwarding information
EP2466814B1 (en) Method, remote access server and system for configuring quality of service
US20190222439A1 (en) Network interworking method, network element, and system
WO2019100924A1 (en) Network performance guarantee method and device
CN105357445A (en) Internet of things system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant