WO2020020249A1 - 一种网络管理方法和装置 - Google Patents

一种网络管理方法和装置 Download PDF

Info

Publication number
WO2020020249A1
WO2020020249A1 PCT/CN2019/097562 CN2019097562W WO2020020249A1 WO 2020020249 A1 WO2020020249 A1 WO 2020020249A1 CN 2019097562 W CN2019097562 W CN 2019097562W WO 2020020249 A1 WO2020020249 A1 WO 2020020249A1
Authority
WO
WIPO (PCT)
Prior art keywords
data set
configuration data
response message
request
message
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.)
Ceased
Application number
PCT/CN2019/097562
Other languages
English (en)
French (fr)
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 EP19841404.7A priority Critical patent/EP3823213B1/en
Publication of WO2020020249A1 publication Critical patent/WO2020020249A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • 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
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • 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
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • 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
    • H04L41/0866—Checking the configuration
    • H04L41/0873—Checking configuration conflicts between network elements

Definitions

  • the present application relates to the field of communications, and in particular, to a network management method and device.
  • Network configuration protocol is a protocol that can be used to manage network devices.
  • a network management system can use NETCONF to operate (modify or lock) the configuration data set of a network device, so that it can query, add, modify or Delete the configuration of the network device.
  • the configuration data sets of common network devices include a running data set and a candidate data set.
  • the running data set includes a set of various configuration parameters that the network device is currently running, and each running data set can be locked by only one network device through a NETCONF session. When the session is disconnected, the running data set is automatically released.
  • the candidate data set includes a set of configuration parameters to be run by the network device.
  • the candidate data set can be understood as a cache of configuration data, which does not take effect immediately.
  • the administrator can perform a commit operation, so that all configurations in the data set are executed at once and become the currently running configuration.
  • Each candidate dataset can only be locked by a client through a NETCONF session. When the session is disconnected, the candidate dataset is automatically released.
  • a configuration data set can be locked by a lock operation in order to monopolize the operation right of the configuration data set.
  • other NETCONF clients cannot operate on the configuration data set (using the configuration data set) until the data set is released.
  • customer A and customer B operate on the same configuration data set through NETCONF
  • customer A locks the configuration data set first
  • customer B cannot modify or lock the configuration data set.
  • the client B has two options: 1) forcibly disconnect (KILL) the session of the client A configuration data set; and 2) wait for the configuration data set to be unlocked.
  • KILL forcibly disconnect
  • the disadvantages of the above two options are: 1) the session of customer A will be forcibly disconnected by customer B, which will affect the business processing of customer A; 2) customer B may wait forever, which will affect the business processing of customer B.
  • the embodiments of the present application provide a network management method and apparatus, which can reduce the impact on the user's service after multiple devices conflict with the operation of the configuration data set.
  • an embodiment of the present application provides a network management method, including: a first device receiving a first request message sent by a second device according to NETCONF, and locking a configuration data set of the first device according to the first request message; The first device receives a second request message sent by a third device according to NETCONF, where the second request message is used to request modification or locking of the configuration data set; the first device sends a first response message to the second device, The first response message is used to notify the third device to request to modify or lock the configuration data set.
  • the first device may notify the second device that locks the configuration data set through a first response message, and there is another device (third device) that needs to operate the configuration data set. So that the second device can release its locked configuration data set as soon as possible, thereby reducing the impact of the usage of the configuration data set on the services of other devices, and improving the efficiency of network management.
  • the first response message includes information of the third device; wherein the information of the third device includes: an internet protocol (IP) address of the third device and the third device At least one of a user's identity (ID) of the device.
  • IP internet protocol
  • the information of the third device may include the IP address of the third device.
  • the information of the third device may include a user identification (user name) of the third device.
  • the information of the third device may include the IP address of the third device and the user identification of the third device.
  • the second device may send a notification message to the third device according to the information of the third device, and the notification message is used to indicate that the configuration data set has been released. This can prevent the third device from making unnecessary waits.
  • the first device sends a second response message to the third device, and the second response message includes information about the second device; wherein the information about the second device includes: the second device At least one of an IP address of the device and a user identification of the second device. That is, the information of the second device may include an IP address of the second device. Alternatively, the information of the second device may include a user identification of the second device. Alternatively, the information of the second device may include an IP address of the second device and a user identifier of the second device.
  • the third device may actively negotiate with the second device based on the information of the second device, so that the second device releases its locked configuration as soon as possible. Data set, so that the third device can use the configuration data set normally as soon as possible. Thereby, the impact of the use of the configuration data set on the service of the third device can be reduced.
  • the method further includes: when the first device determines that the third device forcibly disconnects the session between the second device and the first device, the first device sends to the second device An instruction message for instructing the third device to forcibly disconnect a session between the second device and the first device.
  • the second device can negotiate with the third device to ensure that the services of the second device can continue to be performed, thereby reducing the conflict between the use of the configuration data set and the service bandwidth of the second device. Coming influence.
  • an embodiment of the present application provides a network management method, including: a second device sends a first request message to a first device according to NETCONF, where the first request message is used to lock a configuration data set of the first device; The second device receives a first response message sent by the first device, and the first response message is used to notify a third device to request to modify or lock the configuration data set.
  • the second device can learn that the locked configuration has a conflict with the first response message, so that the second device can release its locked configuration data set as soon as possible, thereby reducing the use of the configuration data set to conflict with the services of the third device Impact.
  • the first response message includes information of a third device
  • the information of the third device includes: an Internet Protocol IP address of the third device and a user identifier of the third device. at least one.
  • the method further includes: after the second device releases the data set of the first device, the second device sends a notification message to the third device, where the notification message is used to indicate the configuration The dataset is released.
  • an embodiment of the present application provides a network management method, including: a third device sends a second request message to a first device according to NETCONF, where the second request message is used to request modification or lock of configuration data of the first device.
  • the third device receives a second response message sent by the first device, and the second response message includes information of the second device that has locked the configuration data set.
  • the first device may notify the third device through a second response message that the configuration data set is locked by the second device, so that the third device may communicate with the The two devices actively negotiate, for example, requesting the second device to release the locked configuration data set as soon as possible, thereby reducing the impact of the use of the configuration data set on the service of the third device.
  • the information of the second device includes at least one of an IP address of the second device and a user identifier of the second device.
  • the third device can negotiate with the second device according to the IP address of the second device or the user identification of the second device, so that the third device can normally use the configuration data set.
  • the method further includes: the third device sends a third request message to the second device, and the third request The message is used to request the second device to release the configuration data set.
  • an embodiment of the present application provides a first device, including: a receiving unit, configured to receive a first request message sent by a second device according to NETCONF, and lock configuration data of the first device according to the first request message
  • the receiving unit is further configured to receive a second request message sent by the third device according to NETCONF, the second request message is used to request modification or locking of the configuration data set;
  • the sending unit is configured to send the first device to the second device A response message, the first response message is used to notify the third device to request to modify or lock the configuration data set.
  • the first response message includes information about the third device, and the information about the third device includes: at least one of an IP address of the third device and a user identifier of the third device.
  • the information about the third device includes: at least one of an IP address of the third device and a user identifier of the third device.
  • the sending unit is further configured to send a second response message to the third device, where the second response message includes information about the second device, where the information about the second device includes: At least one of an IP address of the second device and a user identification of the second device.
  • the sending unit is further configured to: when the third device forcibly disconnects the session between the second device and the first device, send an instruction message to the second device, where the instruction message is used for And instructing the third device to forcibly disconnect the session between the second device and the first device.
  • an embodiment of the present application provides a second device, including: a sending unit, configured to send a first request message to a first device according to NETCONF, where the first request message is used to lock a configuration data set of the first device
  • a receiving unit configured to receive a first response message sent by the first device, where the first response message is used to notify a third device to request to modify or lock the configuration data set.
  • the first response message includes information of a third device; wherein the information of the third device includes: at least one of an IP address of the third device and a user identifier of the third device .
  • the sending unit is further configured to: after the second device releases the data set of the first device, send a notification message to the third device, where the notification message is used to indicate the configuration data set Released.
  • an embodiment of the present application provides a third device, including: a sending unit, configured to send a second request message to the first device according to NETCONF, where the second request message is used to request modification or lock of the first device A configuration data set; a receiving unit, configured to receive a second response message sent by the first device, where the second response message includes information about a second device that has locked the configuration data set.
  • the information of the second device includes at least one of an IP address of the second device and a user identifier of the second device.
  • the sending unit is further configured to send a third request message to the second device, where the third request message is used for Requesting the second device to release the configuration data set.
  • an embodiment of the present application provides a device.
  • the device exists in the form of a chip product.
  • the structure of the device includes a processor and a memory.
  • the memory is used for coupling with the processor and stores program instructions necessary for the device.
  • the processor is configured to execute program instructions stored in the memory, so that the apparatus executes the first aspect of the above method and the first device in any one of the implementation methods, the second aspect, and the second device in any one of the implementation methods, Or the function of the third device in the third aspect and any one of the implementation manners.
  • an embodiment of the present application provides a first device, a second device, or a third device.
  • the first device, the second device, or the third device may implement the corresponding functions in the foregoing method embodiments. It can be implemented by hardware, and it can also be implemented by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the structure of the first device, the second device, or the third device includes a processor and a communication interface, and the processor is configured to support execution of the first device, the second device, or the third device.
  • the communication interface is used to support communication between the first device, the second device, or the third device and other network elements.
  • the first device, the second device, or the third device may further include a memory, which is used for coupling with the processor, and stores program instructions and data necessary for the first device, the second device, or the third device.
  • an embodiment of the present application provides a computer-readable storage medium including instructions that, when run on a computer, cause the computer to execute any one of the methods provided in the first aspect, the second aspect, or the third aspect.
  • an embodiment of the present application provides a computer program product containing instructions, which when executed on a computer, causes the computer to execute any one of the methods provided in the first aspect, the second aspect, or the third aspect.
  • a system for network management includes a first device provided by the fourth aspect and a second device provided by the fifth aspect, and may further include a third device provided by the sixth aspect. among them:
  • the second device configured to send a first request message to the first device according to the NETCONF, and the first request message is used to lock a configuration data set of the first device
  • the first device configured to receive a first request message sent by the second device according to NETCONF, and lock the configuration data set of the first device according to the first request message;
  • the third device configured to send a second request message to the first device according to the NETCONF, and the second request message is used to request to modify or lock the configuration data set of the first device;
  • the first device further configured to receive a second request message sent by the third device according to NETCONF, where the second request message is used to request modification or locking of the configuration data set;
  • the first device further configured to send a first response message to the second device, where the first response message is used to notify the third device to request to modify or lock the configuration data set;
  • the second device is further configured to receive a first response message sent by the first device, where the first response message is used to notify the third device to request to modify or lock the configuration data set.
  • FIG. 1 is a schematic diagram of a communication architecture applicable to a network management method according to an embodiment of the present application
  • FIG. 2 is a schematic diagram of a network management method according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of an internal structure of a first device according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of an internal structure of still another first device according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of an internal structure of a second device according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of an internal structure of still another second device according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of an internal structure of a third device according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of an internal structure of still another third device according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a network management system according to an embodiment of the present application.
  • the embodiments of the present application provide a network management method and apparatus, which are applied to a scenario in which conflicts occur when multiple devices operate on the same configuration data set through NETCONF.
  • operating the configuration data set includes modifying or locking the configuration data set.
  • modifying the configuration data set includes deleting, adding, or replacing various configuration parameters in the configuration data set.
  • configuration data set 1 includes configuration parameters a, b, and c.
  • Modifying configuration data set 1 can be adding new configuration parameter d to configuration data set 1, or deleting configuration parameter a in configuration data set 1.
  • FIG. 1 it may be applied to a scenario in which the second device and the third device operate a certain configuration data set (for example, a candidate data set) of the first device through NETCONF.
  • FIG. 1 is a schematic diagram of a system architecture applicable to a network management method according to an embodiment of the present application, including a first device, a second device, and a third device.
  • the first device may be configured to receive a first request message and a second request message respectively sent by the second device and the third device according to the NETCONF.
  • the first request message is used to lock the configuration data set of the first device.
  • the first device may lock the configuration data set according to the first request message.
  • the second request message is used to request that the configuration data set of the first device be modified or locked after the second device locks the configuration data set of the first device. In this way, the locking operation of the configuration data set by the second device and the modification or locking operation of the configuration data set by the third device conflict.
  • the first device may send a first response message to the second device, and the first response message is used to notify the third device to request to modify or lock the configuration data set. Therefore, the second device can learn that the configuration data set locked by the second device conflicts and needs to be released as soon as possible so that the third device can be used normally.
  • the first device may be a network device, for example, a router, a switch, a firewall, or the like; or a network operating system (software platform) installed on a virtual machine, such as a virtual router, a virtual switch, or a virtual firewall.
  • a network operating system software platform installed on a virtual machine, such as a virtual router, a virtual switch, or a virtual firewall. This application is not limited.
  • the second device and the third device can configure and manage the first device.
  • the second device and the third device can be network devices, such as a client, or network operating systems installed on a virtual machine, such as Windows, MAC, and Linux.
  • the first device in FIG. 2 may be the first device in FIG. 1
  • the second device in FIG. 2 may be the first device in FIG. 1.
  • Equipment, the method comprising:
  • the second device sends a first request message to the first device according to the NETCONF, and the first request message is used to lock the configuration data set of the first device.
  • the second device may encapsulate the first request message into a NETCONF message.
  • the configuration data set of the first device is, for example but not limited to, a running data set or a candidate data set.
  • the data in the configuration data set may include static data and status data, static data such as static IP addresses and virtual local area network (VLAN) nodes, and the like; status data such as count statistics of received, dropped, and forwarded data packets.
  • static data such as static IP addresses and virtual local area network (VLAN) nodes, and the like
  • status data such as count statistics of received, dropped, and forwarded data packets.
  • the first device receives a first request message sent by the second device according to the NETCONF, and locks the configuration data set of the first device according to the first request message.
  • the first device may set the running data set to the locked state, and send a response message to the second device, and inform the first through the response message.
  • the running data set of the device has been locked by the second device.
  • the third device sends a second request message to the first device according to the NETCONF.
  • the second request message is used to request to modify or lock the configuration data set of the first device.
  • the third device may encapsulate the second request message into a NETCONF message.
  • the first device receives a second request message sent by the third device according to the NETCONF, and the second request message is used to request modification or lock of the configuration data set.
  • the third device cannot modify or lock the configuration data set of the first device.
  • the first device determines that the locking operation of the configuration data set by the second device and the modification or locking operation of the configuration data set by the third device conflict.
  • the first device sends a first response message to the second device, and the first response message is used to notify the third device to request to modify or lock the configuration data set.
  • the first response message may include an identification of the conflicting configuration data set.
  • the second device can learn through the first response message that the configuration data set locked by it has conflicted and needs to be released as soon as possible so that the other device (third device) can be used normally.
  • the first response message may include information of the third device.
  • the information of the third device may include an IP address of the third device.
  • the information of the third device may include a user identification (user name) of the third device.
  • the information of the third device may include the IP address of the third device and the user identification of the third device.
  • the user name can be obscured. For example, replace the user name with an "*".
  • the second device can know through the first response message that the third device needs to modify or lock the configuration data set locked by itself, and the configuration data set should be released as soon as possible so that the third device can use the configuration data set normally.
  • the first device may encapsulate the first response message into a NETCONF message, and adopt an extensible markup language (XML) encoding method (for details, refer to the relevant provisions of NETCONF's RFC6241) .
  • XML extensible markup language
  • the structure of the NETCONF message may be as follows (where the symbol "-" "represents a comment on the corresponding message):
  • the second device receives a first response message sent by the first device.
  • the second device can learn that the other device (the third device) needs to modify or lock the configuration data set locked by itself through the first response message, and should release the configuration data set as soon as possible so that the third device can use the configuration data set normally.
  • the second device may send a notification message to the third device, where the notification message is used to indicate that the configuration data set has been released. This can prevent the third device from making unnecessary waits.
  • the second device can negotiate with the third device through corresponding messages to ensure that the second device communicates with the third device.
  • the business on the first device can resume and continue.
  • the first device sends a second response message to the third device, and the second response message includes information of the second device.
  • the information of the second device may include an IP address of the second device.
  • the information of the second device may include a user identification of the second device.
  • the information of the second device may include an IP address of the second device and a user identifier of the second device. If user identification involves security, the user identification can be obscured. For example, replace the user ID with a "*".
  • steps 205 and 206 may not be performed, that is, after step 204 is performed, step 207 may be directly performed.
  • steps 205 and 206 may be performed after steps 207 and 208, and the order of execution between the steps is not specifically limited in this embodiment.
  • the first device may encapsulate the second response message into a NETCONF message and adopt an XML encoding method.
  • the structure of the NETCONF message may be as follows (where the symbol "-" "represents a comment on the corresponding message):
  • the third device receives a second response message sent by the first device, and the second response message includes information of the second device that locks the configuration data set.
  • the third device may send a third request message to the second device, and the third request message is used to request the second device to release the configuration data set, so that the third device can use the configuration data set normally.
  • the first device determines that the third device forcibly disconnects the session between the second device and the first device
  • the first device sends an instruction message to the second device, and the instruction message is used to instruct the third device to forcibly disconnect.
  • the instruction message is used to instruct the third device to forcibly disconnect.
  • the second device receives the indication message.
  • the second device may negotiate with the third device through a corresponding message to ensure that the service of the second device can continue.
  • the first device may notify the second device that locks the configuration data set through a first response message, and other devices (third devices) need to use the configuration data set. So that the second device can release its locked configuration data set as soon as possible, thereby reducing the impact of the usage of the configuration data set on the services of other devices.
  • the first response message may carry information of the third device. Furthermore, after the second device releases the locked data set, the second device may send a notification message to the third device according to the information of the third device, and the notification message is used to indicate that the configuration data set has been released. This can prevent the third device from making unnecessary waits.
  • the first device may send a second response message to the third device, and the second response message includes information of the second device, so that the third device may send a third request message to the second device, and the third request message is used to request the first
  • the second device releases the configuration data set.
  • the third device can actively negotiate with the second device so that the second device releases its locked configuration data set as soon as possible, so that the third device can Use the configuration data set as soon as possible. Thereby, the impact of the use of the configuration data set on the service of the third device can be reduced.
  • the first device, the second device, and the third device include a hardware structure and / or a software module corresponding to each function.
  • the present application can be implemented in hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
  • the first device, the second device, and the third device may be divided into functional modules according to the foregoing method example.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated.
  • a processing module In a processing module.
  • the above integrated modules may be implemented in the form of hardware or software functional modules. It should be noted that the division of the modules in the embodiments of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • FIG. 3 shows a possible structural diagram of the first device 3 involved in the foregoing embodiment.
  • the first device includes a receiving unit 301 and a sending unit 302.
  • the receiving unit 301 may be configured to receive a first request message sent by the second device according to NETCONF, and lock the configuration data set of the first device according to the first request message; it is also configured to receive a third device according to NETCONF.
  • the second request message is sent, and the second request message is used to request to modify or lock the configuration data set.
  • the sending unit 302 is configured to send a first response message to the second device, and the first response message is used to notify the third device to request to modify or lock the configuration data set.
  • the first device in FIG. 3 may be the first device in FIGS. 1 and 2, and may implement the functions of the first device in FIG. 2.
  • the receiving unit 301 may be configured to support the first device to perform the processes 202 and 204 in FIG. 2.
  • the sending unit 302 is configured to support the first device to perform the processes 205, 207, and 209 in FIG. 2.
  • the first device 400 may be a router or a switch or a firewall or other network device with a forwarding function.
  • the first device 400 can implement the functions of the first device in the foregoing method embodiments.
  • the first device 400 includes a main control board 401 and an interface board 402.
  • the main control board 401 includes a processor 403 and a memory 404.
  • the interface board 402 includes a processor 405, a memory 406, and an interface card 407.
  • the main control board 401 and the interface board 402 are coupled.
  • the processor 403 or the processor 405 may be a central processing unit (CPU), a micro processing unit, a general-purpose processing unit, a digital signal processing unit (DSP), and an application-specific integrated circuit (application-specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processing unit
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • the memory 404 or the memory 406 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM), or can store information and instructions
  • ROM read-only memory
  • RAM random access memory
  • Other types of dynamic storage devices can also be electrically erasable programmable read-only memory (electrically, programmable, read-only memory (EEPROM), compact disc (read-only memory, CD-ROM) or other optical disk storage , Optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures Any other medium that can be accessed by a computer, but is not limited to this.
  • EEPROM electrically erasable programmable read-only memory
  • CD-ROM compact disc
  • Optical disc storage including compact discs, laser discs, optical discs, digital versatile discs,
  • the memory 406 may be used to store the program code of the interface board 402, and the processor 405 is used to call the program code in the memory 406 to trigger the interface card 407 to execute the first method in the foregoing method embodiment.
  • the processor 405 calls the program code in the memory 406 to trigger the interface card 407 to support the first device 400 to perform the processes 202, 204, 205, 207, and 209 in FIG. 2.
  • the memory 404 may be used to store the program code and data of the main control board 401, and the processor 403 is used to call the program code in the memory 404 to perform other processing except for information transmission and reception of the first device in the foregoing method embodiment.
  • the processor 403 is used to call the program code in the memory 404 to perform other processing except for information transmission and reception of the first device in the foregoing method embodiment.
  • the specific implementation process please refer to the detailed description of the corresponding steps in the embodiment shown in FIG. 2 above, which will not be repeated one by one here.
  • FIG. 5 illustrates a possible structural diagram of the second device 5 involved in the foregoing embodiment.
  • the second device includes a sending unit 501 and a receiving unit 502.
  • the sending unit 501 is configured to send a first request message to the first device according to the NETCONF, and the first request message is used to lock the configuration data set of the first device.
  • the receiving unit 502 is configured to receive a first response message sent by a first device, where the first response message is used to notify a third device to request to modify or lock a configuration data set.
  • the second device in FIG. 5 may be the second device in FIGS. 1 and 2, and may implement the functions of the second device in FIG. 2.
  • the sending unit 501 is configured to support the second device to perform the process 201 in FIG. 2.
  • the receiving unit 502 is configured to support the second device to execute the process 206 in FIG. 2.
  • the second device may be implemented by the structure (apparatus or system) in FIG. 6.
  • FIG. 6 is a schematic diagram of a structure provided by an embodiment of the present application.
  • the structure 600 includes at least one processor 601, a communication bus 602, a memory 603, and at least one communication interface 604.
  • the processor 601 may be a CPU, a micro-processing unit, a general-purpose processing unit, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • the communication bus 602 may include a path for transmitting information between the aforementioned components.
  • the communication interface 604 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 603 may be ROM or other types of static storage devices capable of storing static information and instructions, RAM or other types of dynamic storage devices capable of storing information and instructions, and may also be EEPROM, CD-ROM or other optical disk storage, optical disk storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • the memory may exist independently and be connected to the processing unit through a bus. The memory can also be integrated with the processing unit.
  • the memory 603 is configured to store application program code for executing the solution of the present application, and the processor 601 controls execution.
  • the processor 601 is configured to execute application program code stored in the memory 603, so as to implement functions in the method of the present application.
  • the processor 601 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 6.
  • the structure 600 may include multiple processors, such as the processor 601 and the processor 607 in FIG. 6. Each of these processors may be a single-CPU processor or a multi-CPU processor.
  • a processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).
  • the structure 600 may be a router, a switch, or a device having a similar structure in FIG. 6.
  • the embodiment of the present application does not limit the type of the structure 600.
  • the structure 600 may further include an output device 605 and an input device 606.
  • the output device 605 communicates with the processor 601 and can display information in a variety of ways.
  • the output device 605 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • the input device 606 is in communication with the processor 601 and can accept user input in a variety of ways.
  • the input device 606 may be a mouse, a keyboard, a touch screen device, or a sensing device.
  • the structure 600 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or the like in FIG. 6 Structure of equipment.
  • PDA personal digital assistant
  • the embodiment of the present application does not limit the type of the structure 600.
  • the second device 600 may implement the functions of the second device in the embodiment shown in FIG. 2.
  • the communication interface 604 may be configured to perform various information transmission and reception performed by the second device in the foregoing method embodiments.
  • the communication interface 604 is used to support the second device 600 to perform the processes 201 and 206 in FIG. 2.
  • the processor 601 is configured to support the second device 600 to perform processes other than information transmission and reception in the technology described herein.
  • the memory 601 is configured to store a program code and data of the second device 600.
  • For the specific implementation process please refer to the detailed description of the corresponding steps in the embodiment shown in FIG. 2 above, which will not be repeated one by one here.
  • FIG. 7 shows a possible structural diagram of the third device 7 involved in the foregoing embodiment.
  • the third device includes a sending unit 701 and a receiving unit 702.
  • the sending unit 701 is configured to send a second request message to the first device according to the NETCONF, and the second request message is used to request to modify or lock the configuration data set of the first device;
  • the receiving unit 702 is configured to: For receiving a second response message sent by the first device, the second response message includes information of the second device that locks the configuration data set.
  • the third device in FIG. 7 may be the third device in FIGS. 1 and 2, and may implement the functions of the third device in FIG. 2.
  • the sending unit 701 is configured to support the third device to perform the process 203 in FIG. 2; the receiving unit 702 is configured to support the third device to perform the process 208 in FIG. 2.
  • the third device may be implemented by the structure (apparatus or system) in FIG. 8.
  • FIG. 8 is a schematic diagram of a structure provided by an embodiment of the present application.
  • the structure 800 includes at least one processor 801, a communication bus 802, a memory 803, and at least one communication interface 804.
  • the processor 801 may be a CPU, a micro-processing unit, a general-purpose processing unit, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • the communication bus 802 may include a path for transmitting information between the aforementioned components.
  • the communication interface 804 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, RAN, and WLAN.
  • the memory 803 may be ROM or other types of static storage devices capable of storing static information and instructions, RAM or other types of dynamic storage devices capable of storing information and instructions, and may also be EEPROM, CD-ROM or other optical disk storage, optical disk storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • the memory may exist independently and be connected to the processing unit through a bus. The memory can also be integrated with the processing unit.
  • the memory 803 is configured to store application program code that executes the solution of the present application, and is controlled and executed by the processor 801.
  • the processor 801 is configured to execute application program code stored in the memory 803, so as to implement functions in the method of the present application.
  • the processor 801 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 8.
  • the structure 800 may include multiple processors, such as the processor 801 and the processor 807 in FIG. 8. Each of these processors can be a single-core processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).
  • the structure 800 may be a client or a device having a similar structure in FIG. 8.
  • the embodiment of the present application does not limit the type of the structure 800.
  • the structure 800 may further include an output device 805 and an input device 806.
  • the output device 805 communicates with the processor 801 and can display information in a variety of ways.
  • the output device 805 may be an LCD, an LED display device, a CRT display device, or a projector.
  • the input device 806 is in communication with the processor 801 and can accept user input in a variety of ways.
  • the input device 806 may be a mouse, a keyboard, a touch screen device, or a sensing device.
  • the structure 800 may be a desktop computer, a portable computer, a network server, a PDA, a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or a device having a similar structure in FIG. 8.
  • the embodiment of the present application does not limit the type of the structure 800.
  • the third device 800 may implement the functions of the third device in the embodiment shown in FIG. 2.
  • the communication interface 804 may be configured to perform various information transmission and reception performed by the third device in the foregoing method embodiment.
  • the communication interface 804 is used to support the third device 800 to perform the processes 203 and 208 in FIG. 2.
  • the processor 801 is configured to support the third device 800 to perform processes other than information transmission and reception in the third device in the technology described herein.
  • the memory 801 is configured to store a program code and data of the third device 800.
  • For the specific implementation process please refer to the detailed description of the corresponding steps in the embodiment shown in FIG. 2 above, which will not be repeated one by one here.
  • An embodiment of the present application further provides a computer-readable storage medium including instructions that, when run on a computer, cause the computer to execute the foregoing network management method.
  • An embodiment of the present application further provides a computer program product containing instructions, which when executed on a computer, causes the computer to execute the above network management method.
  • An embodiment of the present application further provides a device.
  • the device exists in the form of a chip product.
  • the device includes a processor, a memory, and a transceiver component.
  • the transceiver component includes an input-output circuit.
  • the memory is used to store a computer to execute an instruction.
  • the computer executes instructions stored in the memory to implement the above network management method.
  • an execution subject that executes the method provided in the embodiment of the present application may be a chip.
  • an embodiment of the present application provides a network management system 900 suitable for a network management method.
  • the system 900 is configured to implement the network management method in the foregoing method embodiment.
  • the system 900 includes a first device 901 and a second device 902.
  • the system 900 further includes a third device 903.
  • the first device 901, the second device 902, and the third device 903 may implement the functions of the first device, the second device, and the third device in the embodiment shown in FIG. 2, respectively.
  • the first device 901 is used to perform the processes 202, 204, 205, 207, and 209 in FIG. 2, and / or other processes performed by the first device in the technology described herein.
  • the second device 902 is configured to perform the processes 201 and 206 in FIG. 2 and / or other processes performed by the second device in the technology described herein.
  • the third device 903 is used to perform the processes 203 and 208 in FIG. 2 and / or other processes performed by the third device in the technology described herein.
  • Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that can be accessed by a general purpose or special purpose computer.
  • the embodiments of the present application may be provided as a method, a system, or a computer program product. Therefore, the embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • Embodiments of the present application are described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or block in the flowcharts and / or block diagrams, and combinations of processes and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions.
  • These computer program instructions may be provided to a processing unit of a general-purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, so that the instructions generated by the computer or other programmable data processing device's processing unit generate instructions Means for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to work in a particular manner such that the instructions stored in the computer-readable memory produce a manufactured article including an instruction device, the instructions
  • the device implements the functions specified in one or more flowcharts and / or one or more blocks of the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请实施例提供一种网络管理方法和装置，涉及通信领域，能够减小多个设备对配置数据集的操作发生冲突后给用户的业务带来的影响。其方法为：第一设备接收第二设备根据NETCONF发送的第一请求消息，并根据第一请求消息锁定第一设备的配置数据集；第一设备接收第三设备根据NETCONF发送的第二请求消息，第二请求消息用于请求修改或锁定配置数据集；第一设备向第二设备发送第一响应消息，第一响应消息用于通知第三设备请求修改或锁定配置数据集。本申请实施例应用于多个设备通过NETCONF使用同一个配置数据集时产生冲突的场景。

Description

一种网络管理方法和装置
本申请要求于2018年7月27日提交中国专利局、申请号为201810853147.3、申请名称为“一种网络管理方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种网络管理方法和装置。
背景技术
网络配置协议(network configuration，NETCONF)是一种可以用于管理网络设备的协议，网络管理系统可以利用NETCONF对网络设备的配置数据集进行操作(修改或锁定)，从而可以查询、增加、修改或删除网络设备的配置。常见的网络设备的配置数据集包括运行(running)数据集和候选(candidate)数据集。其中，running数据集包括网络设备当前正在运行的各项配置参数的集合，每个running数据集仅可以被一个网络设备通过NETCONF会话锁定。当会话断开时，running数据集自动释放。candidate数据集包括网络设备将要运行的各项配置参数的集合。candidate数据集可理解为一个配置数据的缓存，并不立即生效，待到合适的时机，管理员可以执行commit操作，令数据集中所有配置一次性全部执行，成为当前运行的配置。每个candidate数据集仅可以被一个客户端通过NETCONF会话锁定，当会话断开时，candidate数据集自动释放。
目前，可以通过锁定(lock)操作对配置数据集加锁，以便独占对该配置数据集的操作权。一旦配置数据集被锁定，则其他NETCONF客户不能对该配置数据集进行操作(使用该配置数据集)，直到该数据集被释放。例如，当客户A和客户B通过NETCONF对同一配置数据集进行操作时，若客户A先锁定了该配置数据集，则客户B无法修改或锁定该配置数据集。此时，客户B可以有两个选择：1)强行断开(KILL)客户A配置数据集的会话；2)等待该配置数据集被解锁。如上两个选择的缺点分别是：1)客户A的会话会被客户B强行断开，从而影响客户A的业务处理；2)客户B可能永久等待，从而影响客户B的业务处理。
发明内容
本申请实施例提供一种网络管理方法和装置，能够减小多个设备对配置数据集的操作发生冲突后给用户的业务带来的影响。
第一方面，本申请实施例提供一种网络管理方法，包括：第一设备接收第二设备根据NETCONF发送的第一请求消息，并根据该第一请求消息锁定该第一设备的配置数据集；该第一设备接收第三设备根据NETCONF发送的第二请求消息，其中，该第二请求消息用于请求修改或锁定该配置数据集；该第一设备向该第二设备发送第一响应消息，该第一响应消息用于通知该第三设备请求修改或锁定该配置数据集。
基于上述方案，当出现配置数据集使用冲突时，第一设备可以通过第一响应消息 告知锁定配置数据集的第二设备，有其他设备(第三设备)需要对该配置数据集进行操作。以便第二设备可以尽快释放其锁定的配置数据集，从而减小配置数据集使用冲突对其他设备的业务的影响，提高了网络管理的效率。
在一种可能的实现方式中，该第一响应消息包括该第三设备的信息；其中，该第三设备的信息包括：该第三设备的网际协议(internet protocol，IP)地址和该第三设备的用户标识(Identity，ID)中的至少一个。
也就是说，第三设备的信息可以包括第三设备的IP地址。或者，第三设备的信息可以包括第三设备的用户标识(用户名)。或者，第三设备的信息可以包括第三设备的IP地址和第三设备的用户标识。进而，当第二设备释放该锁定的数据集后，第二设备可以根据第三设备的信息向第三设备发送通知消息，通知消息用于指示配置数据集已释放。这样可以避免第三设备做无谓的等待。
在一种可能的实现方式中，该第一设备向该第三设备发送第二响应消息，该第二响应消息包括该第二设备的信息；其中，该第二设备的信息包括：该第二设备的IP地址和该第二设备的用户标识中的至少一个。即，第二设备的信息可以包括第二设备的IP地址。或者，第二设备的信息可以包括第二设备的用户标识。或者，第二设备的信息可以包括第二设备的IP地址和第二设备的用户标识。
这样一来，当第二设备和第三设备对配置数据集的使用发生冲突时，第三设备可以根据第二设备的信息主动与第二设备进行协商，以便第二设备尽快释放其锁定的配置数据集，使第三设备可以尽快正常使用该配置数据集。从而可以减小配置数据集的使用发生冲突给第三设备的业务带来的影响。
在一种可能的实现方式中，该方法还包括：当该第一设备确定该第三设备强行断开该第二设备与该第一设备的会话时，该第一设备向该第二设备发送指示消息，该指示消息用于指示该第三设备强行断开该第二设备与该第一设备的会话。
这样，当第二设备接收到指示消息后，第二设备可以与第三设备进行协商，保证第二设备的业务可以继续进行，从而减小配置数据集的使用发生冲突给第二设备的业务带来的影响。
第二方面，本申请实施例提供一种网络管理方法，包括：第二设备根据NETCONF向第一设备发送第一请求消息，该第一请求消息用于锁定该第一设备的配置数据集；该第二设备接收该第一设备发送的第一响应消息，该第一响应消息用于通知第三设备请求修改或锁定该配置数据集。
基于上述方案，第二设备可以通过第一响应消息获知其锁定的配置发生使用冲突，以便第二设备可以尽快释放其锁定的配置数据集，从而减小配置数据集使用冲突对第三设备的业务的影响。
在一种可能的实现方式中，该第一响应消息包括第三设备的信息；其中，该第三设备的信息包括：该第三设备的网际协议IP地址和该第三设备的用户标识中的至少一个。
在一种可能的实现方式中，该方法还包括：当该第二设备释放该第一设备的数据集后，该第二设备向该第三设备发送通知消息，该通知消息用于指示该配置数据集已 释放。
第三方面，本申请实施例提供一种网络管理方法，包括：第三设备根据NETCONF向第一设备发送第二请求消息，该第二请求消息用于请求修改或锁定该第一设备的配置数据集；该第三设备接收该第一设备发送的第二响应消息，该第二响应消息包括已经锁定该配置数据集的第二设备的信息。
基于上述方案，当出现配置数据集使用冲突时，第一设备可以通过第二响应消息告知第三设备该配置数据集已被第二设备锁定，以便第三设备可以根据第二设备的信息与第二设备主动协商，例如请求第二设备尽快释放锁定的配置数据集，从而减小配置数据集使用冲突对第三设备的业务的影响。
在一种可能的实现方式中，该第二设备的信息包括：该第二设备的IP地址和该第二设备的用户标识中的至少一个。
这样，第三设备可以根据第二设备的IP地址或第二设备的用户标识与第二设备进行协商，以便第三设备可以正常使用该配置数据集。
在一种可能的实现方式中，该第三设备接收该第一设备发送的第二响应消息之后，该方法还包括：该第三设备向该第二设备发送第三请求消息，该第三请求消息用于请求该第二设备释放该配置数据集。
第四方面，本申请实施例提供一种第一设备，包括：接收单元，用于接收第二设备根据NETCONF发送的第一请求消息，并根据该第一请求消息锁定该第一设备的配置数据集；该接收单元，还用于接收第三设备根据NETCONF发送的第二请求消息，该第二请求消息用于请求修改或锁定该配置数据集；发送单元，用于向该第二设备发送第一响应消息，该第一响应消息用于通知该第三设备请求修改或锁定该配置数据集。
在一种可能的实现方式中，该第一响应消息包括该第三设备的信息；其中，该第三设备的信息包括：该第三设备的IP地址和该第三设备的用户标识中的至少一个。
在一种可能的实现方式中，该发送单元还用于：向该第三设备发送第二响应消息，该第二响应消息包括该第二设备的信息；其中，该第二设备的信息包括：该第二设备的IP地址和该第二设备的用户标识中的至少一个。
在一种可能的实现方式中，该发送单元还用于：当该第三设备强行断开该第二设备与该第一设备的会话时，向该第二设备发送指示消息，该指示消息用于指示该第三设备强行断开该第二设备与该第一设备的会话。
第四方面及其各种可能的实现方式的技术效果可以参见第一方面及其各种可能的实现方式的技术效果，此处不再赘述。
第五方面，本申请实施例提供一种第二设备，包括：发送单元，用于根据NETCONF向第一设备发送第一请求消息，该第一请求消息用于锁定该第一设备的配置数据集；接收单元，用于接收该第一设备发送的第一响应消息，该第一响应消息用于通知第三设备请求修改或锁定该配置数据集。
在一种可能的实现方式中，该第一响应消息包括第三设备的信息；其中，该第三设备的信息包括：该第三设备的IP地址和该第三设备的用户标识中的至少一个。
在一种可能的实现方式中，该发送单元还用于：当该第二设备释放该第一设备的 数据集后，向该第三设备发送通知消息，该通知消息用于指示该配置数据集已释放。
第五方面及其各种可能的实现方式的技术效果可以参见第二方面及其各种可能的实现方式的技术效果，此处不再赘述。
第六方面，本申请实施例提供一种第三设备，包括：发送单元，用于根据NETCONF向第一设备发送第二请求消息，该第二请求消息用于请求修改或锁定该第一设备的配置数据集；接收单元，用于接收该第一设备发送的第二响应消息，该第二响应消息包括已锁定该配置数据集的第二设备的信息。
在一种可能的实现方式中，该第二设备的信息包括：该第二设备的IP地址和该第二设备的用户标识中的至少一个。
在一种可能的实现方式中，该第三设备接收该第一设备发送的第二响应消息之后，该发送单元还用于：向该第二设备发送第三请求消息，该第三请求消息用于请求该第二设备释放该配置数据集。
第六方面及其各种可能的实现方式的技术效果可以参见第三方面及其各种可能的实现方式的技术效果，此处不再赘述。
第七方面，本申请实施例提供了一种装置，该装置以芯片的产品形态存在，该装置的结构中包括处理器和存储器，该存储器用于与处理器耦合，保存该装置必要的程序指令和数据，该处理器用于执行存储器中存储的程序指令，使得该装置执行上述方法中第一方面以及任意一个实现方式中的第一设备、第二方面以及任意一个实现方式中的第二设备，或第三方面以及任意一个实现方式中的第三设备的功能。
第八方面，本申请实施例提供了一种第一设备、第二设备或第三设备，该第一设备、第二设备或第三设备可以实现上述方法实施例中相应的功能，功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个上述功能相应的模块。
在一种可能的设计中，该第一设备、第二设备或第三设备的结构中包括处理器和通信接口，该处理器被配置为支持该第一设备、第二设备或第三设备执行上述方法中相应的功能。该通信接口用于支持该第一设备、第二设备或第三设备与其他网元之间的通信。该第一设备、第二设备或第三设备还可以包括存储器，该存储器用于与处理器耦合，其保存该第一设备、第二设备或第三设备必要的程序指令和数据。
第九方面，本申请实施例提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行第一方面、第二方面或第三方面提供的任意一种方法。
第十方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行第一方面、第二方面或第三方面提供的任意一种方法。
第十一方面，提供了一种用于网络管理的系统，所述系统包括第四方面提供的第一设备和第五方面提供的第二设备，还可以包括第六方面提供的第三设备。其中：
该第二设备：用于根据NETCONF向第一设备发送第一请求消息，该第一请求消息用于锁定该第一设备的配置数据集
该第一设备：用于接收第二设备根据NETCONF发送的第一请求消息，并根据该第一请求消息锁定该第一设备的配置数据集；
该第三设备：用于根据NETCONF向第一设备发送第二请求消息，该第二请求消 息用于请求修改或锁定该第一设备的配置数据集；
该第一设备：还用于接收第三设备根据NETCONF发送的第二请求消息，该第二请求消息用于请求修改或锁定该配置数据集；
该第一设备：还用于向该第二设备发送第一响应消息，该第一响应消息用于通知该第三设备请求修改或锁定该配置数据集；
该第二设备：还用于接收该第一设备发送的第一响应消息，该第一响应消息用于通知该第三设备请求修改或锁定该配置数据集。
附图说明
图1为本申请实施例提供的一种适用于网络管理方法的通信架构示意图；
图2为本申请实施例提供的一种用于网络管理方法的示意图；
图3为本申请实施例提供的一种第一设备的内部结构示意图；
图4为本申请实施例提供的又一种第一设备的内部结构示意图；
图5为本申请实施例提供的一种第二设备的内部结构示意图；
图6为本申请实施例提供的又一种第二设备的内部结构示意图；
图7为本申请实施例提供的一种第三设备的内部结构示意图；
图8为本申请实施例提供的又一种第三设备的内部结构示意图；
图9为本申请实施例提供的一种网络管理系统示意图。
具体实施方式
本申请实施例提供一种网络管理方法和装置，应用于多个设备通过NETCONF对同一个配置数据集进行操作时产生冲突的场景。其中，对配置数据集进行操作包括对该配置数据集进行修改或锁定。具体的，对配置数据集进行修改包括对配置数据集中的各项配置参数进行删除、增加或替换等。例如，假设配置数据集1包括配置参数a、b和c，对配置数据集1进行修改可以是向配置数据集1中添加新的配置参数d，或者是删除配置数据集1中的配置参数a，或者是将配置数据集1中的配置参数b替换为配置参数e。示例性的，如图1所示，可以应用于第二设备和第三设备通过NETCONF对第一设备的某配置数据集(例如，candidate数据集)进行操作的场景。
图1为本申请实施例提供的一种适用于网络管理方法的系统架构示意图，包括第一设备、第二设备和第三设备。其中，第一设备可以用于接收第二设备和第三设备根据NETCONF分别发送的第一请求消息和第二请求消息。第一请求消息用于锁定第一设备的配置数据集。第一设备可以根据第一请求消息将配置数据集锁定。第二请求消息用于在第二设备锁定第一设备的配置数据集后，请求修改或锁定该配置数据集。这样，第二设备对配置数据集的锁定操作和第三设备对配置数据集的修改或锁定操作发生冲突。此时，第一设备可以向第二设备发送第一响应消息，第一响应消息用于通知第三设备请求修改或锁定配置数据集。从而第二设备可以获知自身锁定的配置数据集发生了冲突，需要尽快释放，以便第三设备可以正常使用。
其中，第一设备可以为网络设备，例如可以为路由器、交换机、防火墙等；也可以是安装在虚拟机上的网络操作系统(软件平台)，例如虚拟的路由器、虚拟的交换机、虚拟的防火墙等，本申请不做限定。
第二设备和第三设备能够对第一设备进行配置和管理，可以为网络设备，例如客户机；也可以是安装在虚拟机上的网络操作系统，例如Windows、MAC、Linux等网络操作系统。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
本申请实施例提供一种网络管理方法，如图2所示，其中图2中的第一设备可以是图1中的第一设备，图2中的第二设备可以是图1中的第一设备，该方法包括：
201、第二设备根据NETCONF向第一设备发送第一请求消息，第一请求消息用于锁定第一设备的配置数据集。
其中，第二设备可以将第一请求消息封装成NETCONF报文。
第一设备的配置数据集例如但不限于为running数据集或candidate数据集。配置数据集中的数据可以包括静态数据和状态数据，静态数据例如静态IP地址和虚拟局域网(virtual local area network，VLAN)节点等；状态数据例如接收、丢弃、转发的数据包的计数统计等。
202、第一设备接收第二设备根据NETCONF发送的第一请求消息，并根据第一请求消息锁定第一设备的配置数据集。
举例来说，当第一请求消息用于锁定第一设备的running数据集时，第一设备可以将running数据集设置为锁定状态，并向第二设备发送响应消息，通过该响应消息告知第一设备的running数据集已被第二设备锁定。
203、第三设备根据NETCONF向第一设备发送第二请求消息，第二请求消息用于请求修改或锁定第一设备的配置数据集。
其中，第三设备可以将第二请求消息封装成NETCONF报文。
204、第一设备接收第三设备根据NETCONF发送的第二请求消息，第二请求消息用于请求修改或锁定配置数据集。
由于第二设备已经将第一设备的配置数据集锁定，因此第三设备无法修改或锁定第一设备的配置数据集。此时，第一设备确定第二设备对配置数据集的锁定操作和第三设备对配置数据集的修改或锁定操作发生冲突。
205、第一设备向第二设备发送第一响应消息，第一响应消息用于通知第三设备请求修改或锁定所述配置数据集。
在一种可能的设计中，第一响应消息可以包括发生冲突的配置数据集的标识。这样，第二设备可以通过第一响应消息获知自身锁定的配置数据集发生了冲突，需要尽快释放，以便其他设备(第三设备)可以正常使用。
进一步的，第一响应消息可以包括第三设备的信息。其中，第三设备的信息可以包括第三设备的IP地址。或者，第三设备的信息可以包括第三设备的用户标识(用户名)。或者，第三设备的信息可以包括第三设备的IP地址和第三设备的用户标识。其 中，若用户名涉及到安全，则可把用户名模糊化。例如通过“*”号代替用户名。这样，第二设备可以通过第一响应消息获知第三设备需要对自身锁定的配置数据集进行修改或锁定，应该尽快释放该配置数据集，以便第三设备可以正常使用该配置数据集。
在一种可能的设计中，第一设备可以将第一响应消息封装成NETCONF报文，采用可扩展标记语言(extensible markup language，XML)的编码方式(具体可以参考NETCONF的RFC 6241的相关规定)。示例性的，该NETCONF报文的结构可以如下(其中，符号“--》”代表对相应报文的注释)：
Figure PCTCN2019097562-appb-000001
206、第二设备接收第一设备发送的第一响应消息。
其中，第一响应消息的格式可以参考步骤205中的相关描述。
第二设备可以通过第一响应消息获知其他设备(第三设备)需要对自身锁定的配置数据集进行修改或锁定，应该尽快释放该配置数据集，以便第三设备可以正常使用该配置数据集。
可选的，当第二设备释放该锁定的数据集后，第二设备可以向第三设备发送通知消息，通知消息用于指示配置数据集已释放。这样可以避免第三设备做无谓的等待。
另外，若第二设备与第一设备的链接无故断掉，那么很有可能是第三设备强行断掉的，第二设备可以通过相应的消息与第三设备进行协商，以保证第二设备与第一设备的业务可以恢复并继续进行。
207、第一设备向第三设备发送第二响应消息，第二响应消息包括第二设备的信息。
其中，第二设备的信息可以包括第二设备的IP地址。或者，第二设备的信息可以包括第二设备的用户标识。或者，第二设备的信息可以包括第二设备的IP地址和第二设备的用户标识。若用户标识涉及到安全，则可把用户标识模糊化。例如通过“*”号代替用户标识。
在一种可能的设计中，步骤205和206可以不执行，即在执行步骤204之后，可以直接执行步骤207。或者步骤205和206可以在步骤207和步骤208之后再执行，本实施例对各步骤之间的执行先后顺序不作具体限定。
在一种可能的设计中，第一设备可以将第二响应消息封装成NETCONF报文，采用XML的编码方式。示例性的，该NETCONF报文的结构可以如下(其中，符号“--》”代表对相应报文的注释)：
Figure PCTCN2019097562-appb-000002
Figure PCTCN2019097562-appb-000003
208、第三设备接收第一设备发送的第二响应消息，第二响应消息包括锁定配置数据集的第二设备的信息。
其中，第二响应消息的格式可以参考步骤207中的相关描述。
可选的，第三设备可以向第二设备发送第三请求消息，第三请求消息用于请求第二设备释放配置数据集，以便第三设备可以正常使用该配置数据集。
209、可选的，当第一设备确定第三设备强行断开第二设备与第一设备的会话时，第一设备向第二设备发送指示消息，指示消息用于指示第三设备强行断开第二设备与第一设备的会话。
第二设备接收指示消息。第二设备可以通过相应的消息与第三设备进行协商，以保证第二设备的业务可以继续进行。
需要说明的是，步骤201-步骤209之间没有必然的执行先后顺序，本实施例对各步骤之间的执行先后顺序不作具体限定。
基于上述方案，当出现配置数据集使用冲突时，第一设备可以通过第一响应消息告知锁定配置数据集的第二设备，有其他设备(第三设备)需要使用该配置数据集。以便第二设备可以尽快释放其锁定的配置数据集，从而减小配置数据集使用冲突对其他设备的业务的影响。
其中，第一响应消息可以携带第三设备的信息。进而，当第二设备释放该锁定的数据集后，第二设备可以根据第三设备的信息向第三设备发送通知消息，通知消息用于指示配置数据集已释放。这样可以避免第三设备做无谓的等待。
并且，第一设备可以向第三设备发送第二响应消息，第二响应消息包括第二设备的信息，以便第三设备可以向第二设备发送第三请求消息，第三请求消息用于请求第二设备释放配置数据集。这样，当第二设备和第三设备对配置数据集的使用发生冲突时，第三设备可以主动与第二设备进行协商，以便第二设备尽快释放其锁定的配置数据集，使第三设备可以尽快正常使用该配置数据集。从而可以减小配置数据集的使用 发生冲突对第三设备的业务的影响。
上述主要从第一设备、第二设备和第三设备的角度对本申请实施例提供的方案进行了介绍。可以理解的是，第一设备、第二设备和第三设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对第一设备、第二设备和第三设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图3示出了上述实施例中所涉及的第一设备3的一种可能的结构示意图，第一设备包括：接收单元301和发送单元302。在本申请实施例中，接收单元301可以用于接收第二设备根据NETCONF发送的第一请求消息，并根据第一请求消息锁定第一设备的配置数据集；还用于接收第三设备根据NETCONF发送的第二请求消息，第二请求消息用于请求修改或锁定配置数据集。发送单元302用于向第二设备发送第一响应消息，第一响应消息用于通知第三设备请求修改或锁定配置数据集。图3中的第一设备可以是图1和图2中的第一设备，并且可以实现图2中第一设备的功能。其中，接收单元301可以用于支持第一设备执行图2中的过程202和204。发送单元302用于支持第一设备执行图2中过程205、207和209。
参阅图4所示，本申请实施例提供了一种第一设备400。第一设备400可以为路由器或交换器或防火墙或其他有转发功能的网络设备。第一设备400能够实现前述方法实施例中的第一设备的功能。所述第一设备400包括：主控板401和接口板402。主控板401包括：处理器403和存储器404。接口板402包括：处理器405、存储器406和接口卡407。主控板401和接口板402耦合。
其中，处理器403或处理器405可以是一个中央处理单元(central processing unit，CPU)，微处理单元，通用处理单元，数字信号处理单元(digital signal processor，DSP)，专用集成电路(application-specific integrated circuit，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。
存储器404或存储器406可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存 储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
这些硬件可以执行上述方法示例中的相应功能，例如，存储器406可以用于存储接口板402的程序代码，处理器405用于调用存储器406中的程序代码触发接口卡407执行上述方法实施例中第一设备执行的各种信息接收和发送。例如，处理器405调用存储器406中的程序代码触发接口卡407支持第一设备400执行图2中的过程202、204、205、207和209。存储器404可以用于存储主控板401的程序代码和数据，处理器403用于调用存储器404中的程序代码执行上述方法实施例中第一设备除了信息收发之外的其他处理。具体执行过程请参考上述图2所示实施例中相应步骤的详细描述，这里不再一一赘述。
在采用对应各个功能划分各个功能模块的情况下，图5示出了上述实施例中所涉及的第二设备5的一种可能的结构示意图，第二设备包括：发送单元501和接收单元502。在本申请实施例中，发送单元501，用于根据NETCONF向第一设备发送第一请求消息，第一请求消息用于锁定第一设备的配置数据集。接收单元502，用于接收第一设备发送的第一响应消息，第一响应消息用于通知第三设备请求修改或锁定配置数据集。图5中的第二设备可以是图1和图2中的第二设备，并且可以实现图2中第二设备的功能。其中，发送单元501用于支持第二设备执行图2中的过程201。接收单元502用于支持第二设备执行图2中的过程206。
在一种可能的设计中，第二设备可以通过图6中的结构(装置或系统)来实现。
图6所示为本申请实施例提供的一种结构的示意图。结构600包括至少一个处理器601，通信总线602，存储器603以及至少一个通信接口604。
处理器601可以是一个CPU，微处理单元，通用处理单元，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。
通信总线602可包括一通路，在上述组件之间传送信息。
通信接口604，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器603可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是EEPROM、CD-ROM或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理单元相连接。存储器也可以和处理单元集成在一起。
其中，存储器603用于存储执行本申请方案的应用程序代码，并由处理器601来控制执行。处理器601用于执行存储器603中存储的应用程序代码，从而实现本申请方法中的功能。
在具体实现中，作为一种实施例，处理器601可以包括一个或多个CPU，例如图6中的CPU0和CPU1。
在具体实现中，作为一种实施例，结构600可以包括多个处理器，例如图6中的处理器601和处理器607。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，结构600可以是路由器、交换机或有图6中类似结构的设备。本申请实施例不限定结构600的类型。
在具体实现中，作为一种实施例，结构600还可以包括输出设备605和输入设备606。输出设备605和处理器601通信，可以以多种方式来显示信息。例如，输出设备605可以是液晶显示器(liquid crystal display，LCD),发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备606和处理器601通信，可以以多种方式接受用户的输入。例如，输入设备606可以是鼠标、键盘、触摸屏设备或传感设备等。
在具体实现中，结构600可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、通信设备、嵌入式设备或有图6中类似结构的设备。本申请实施例不限定结构600的类型。
该第二设备600可以实现图2所示的实施例中的第二设备的功能。其中，通信接口604可以用于执行上述方法实施例中第二设备执行的各种信息收发。例如，通信接口604用于支持第二设备600执行图2中的过程201和206。处理器601用于支持第二设备600执行本文所描述的技术中第二设备执行除信息收发之外的其它过程。存储器601，用于存储第二设备600的程序代码和数据。具体执行过程请参考上述图2所示实施例中相应步骤的详细描述，这里不再一一赘述。
在采用对应各个功能划分各个功能模块的情况下，图7示出了上述实施例中所涉及的第三设备7的一种可能的结构示意图，第三设备包括：发送单元701和接收单元702。在本申请实施例中，发送单元701，用于根据NETCONF向第一设备发送第二请求消息，该第二请求消息用于请求修改或锁定该第一设备的配置数据集；接收单元702，用于接收该第一设备发送的第二响应消息，该第二响应消息包括锁定该配置数据集的第二设备的信息。图7中的第三设备可以是图1和图2中的第三设备，并且可以实现图2中第三设备的功能。其中，发送单元701用于支持第三设备执行图2中的过程203；接收单元702用于支持第三设备执行图2中的过程208。
在一种可能的设计中，第三设备可以通过图8中的结构(装置或系统)来实现。
图8所示为本申请实施例提供的一种结构的示意图。结构800包括至少一个处理器801，通信总线802，存储器803以及至少一个通信接口804。
处理器801可以是一个CPU，微处理单元，通用处理单元，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。
通信总线802可包括一通路，在上述组件之间传送信息。
通信接口804，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，RAN，WLAN等。
存储器803可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是EEPROM、 CD-ROM或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理单元相连接。存储器也可以和处理单元集成在一起。
其中，存储器803用于存储执行本申请方案的应用程序代码，并由处理器801来控制执行。处理器801用于执行存储器803中存储的应用程序代码，从而实现本申请方法中的功能。
在具体实现中，作为一种实施例，处理器801可以包括一个或多个CPU，例如图8中的CPU0和CPU1。
在具体实现中，作为一种实施例，结构800可以包括多个处理器，例如图8中的处理器801和处理器807。这些处理器中的每一个可以是一个单核处理器，也可以是一个多核处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，结构800可以是客户机或有图8中类似结构的设备。本申请实施例不限定结构800的类型。
在具体实现中，作为一种实施例，结构800还可以包括输出设备805和输入设备806。输出设备805和处理器801通信，可以以多种方式来显示信息。例如，输出设备805可以是LCD，LED显示设备，CRT显示设备，或投影仪等。输入设备806和处理器801通信，可以以多种方式接受用户的输入。例如，输入设备806可以是鼠标、键盘、触摸屏设备或传感设备等。
在具体实现中，结构800可以是台式机、便携式电脑、网络服务器、PDA、移动手机、平板电脑、无线终端设备、通信设备、嵌入式设备或有图8中类似结构的设备。本申请实施例不限定结构800的类型。
第三设备800可以实现图2所示的实施例中的第三设备的功能。其中，通信接口804可以用于执行上述方法实施例中第三设备执行的各种信息收发。例如，通信接口804用于支持第三设备800执行图2中的过程203和208。处理器801用于支持第三设备800执行本文所描述的技术中第三设备执行除信息收发之外的其它过程。存储器801，用于存储第三设备800的程序代码和数据。具体执行过程请参考上述图2所示实施例中相应步骤的详细描述，这里不再一一赘述。
本申请实施例还提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述网络管理方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述网络管理方法。
本申请实施例还提供了一种装置，该装置以芯片的产品形态存在，该装置包括处理器、存储器和收发组件，收发组件包括输入输出电路，存储器用于存储计算机执行指令，处理器通过执行存储器中存储的计算机执行指令实现上述网络管理方法。该情况下，执行本申请实施例提供的方法的执行主体可以为芯片。
参阅图9所示，本申请实施例提供了一种适用于网络管理方法的网络管理系统900， 该系统900用于实现前述方法实施例中的网络管理方法。该系统900包括第一设备901和第二设备902。在一个示例中，该系统900还包括第三设备903。
其中，第一设备901、第二设备902和第三设备903可以分别实现图2所示的实施例中的第一设备、第二设备和第三设备的功能。例如，第一设备901用于执行图2中的过程202、204、205、207和209，和/或用于本文所描述的技术中第一设备执行的其它过程。第二设备902，用于执行图2中的过程201和206，和/或用于本文所描述的技术中第二设备执行的其它过程。第三设备903用于执行图2中的过程203和208，和/或用于本文所描述的技术中第三设备执行的其它过程。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。
本领域内的技术人员应明白，本申请实施例可提供为方法、系统、或计算机程序产品。因此，本申请实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请实施例是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理单元以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理单元执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申 请的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (17)

  1. 一种网络管理方法，其特征在于，包括：
    第一设备接收第二设备根据网络配置协议NETCONF发送的第一请求消息，并根据所述第一请求消息锁定所述第一设备的配置数据集；
    所述第一设备接收第三设备根据NETCONF发送的第二请求消息，所述第二请求消息用于请求修改或锁定所述配置数据集；
    所述第一设备向所述第二设备发送第一响应消息，所述第一响应消息用于通知所述第三设备请求修改或锁定所述配置数据集。
  2. 根据权利要求1所述的网络管理方法，其特征在于，
    所述第一响应消息包括所述第三设备的信息；其中，所述第三设备的信息包括：所述第三设备的网际协议IP地址和所述第三设备的用户标识中的至少一个。
  3. 根据权利要求1或2所述的网络管理方法，其特征在于，所述方法还包括：
    所述第一设备向所述第三设备发送第二响应消息，所述第二响应消息包括所述第二设备的信息；其中，所述第二设备的信息包括：所述第二设备的IP地址和所述第二设备的用户标识中的至少一个。
  4. 根据权利要求1-3任一项所述的网络管理方法，其特征在于，所述方法还包括：
    当所述第一设备确定所述第三设备强行断开所述第二设备与所述第一设备的会话时，所述第一设备向所述第二设备发送指示消息，所述指示消息用于指示所述第三设备强行断开所述第二设备与所述第一设备的会话。
  5. 一种网络管理方法，其特征在于，包括：
    第二设备根据网络配置协议NETCONF向第一设备发送第一请求消息，所述第一请求消息用于锁定所述第一设备的配置数据集；
    所述第二设备接收所述第一设备发送的第一响应消息，所述第一响应消息用于通知第三设备请求修改或锁定所述配置数据集。
  6. 根据权利要求5所述的网络管理方法，其特征在于，
    所述第一响应消息包括所述第三设备的信息；其中，所述第三设备的信息包括：所述第三设备的网际协议IP地址和所述第三设备的用户标识中的至少一个。
  7. 根据权利要求5或6所述的网络管理方法，其特征在于，所述方法还包括：
    当所述第二设备释放所述第一设备的数据集后，所述第二设备向所述第三设备发送通知消息，所述通知消息用于指示所述配置数据集已释放。
  8. 一种第一设备，其特征在于，包括：
    接收单元，用于接收第二设备根据网络配置协议NETCONF发送的第一请求消息，并根据所述第一请求消息锁定所述第一设备的配置数据集；
    所述接收单元，还用于接收第三设备根据NETCONF发送的第二请求消息，所述第二请求消息用于请求修改或锁定所述配置数据集；
    发送单元，用于向所述第二设备发送第一响应消息，所述第一响应消息用于通知所述第三设备请求修改或锁定所述配置数据集。
  9. 根据权利要求8所述的第一设备，其特征在于，
    所述第一响应消息包括所述第三设备的信息；其中，所述第三设备的信息包括： 所述第三设备的网际协议IP地址和所述第三设备的用户标识中的至少一个。
  10. 根据权利要求8或9所述的第一设备，其特征在于，所述发送单元还用于：
    向所述第三设备发送第二响应消息，所述第二响应消息包括所述第二设备的信息；其中，所述第二设备的信息包括：所述第二设备的IP地址和所述第二设备的用户标识中的至少一个。
  11. 根据权利要求8-10任一项所述的第一设备，其特征在于，所述发送单元还用于：
    当所述第三设备强行断开所述第二设备与所述第一设备的会话时，向所述第二设备发送指示消息，所述指示消息用于指示所述第三设备强行断开所述第二设备与所述第一设备的会话。
  12. 一种第二设备，其特征在于，包括：
    发送单元，用于根据网络配置协议NETCONF向第一设备发送第一请求消息，所述第一请求消息用于锁定所述第一设备的配置数据集；
    接收单元，用于接收所述第一设备发送的第一响应消息，所述第一响应消息用于通知第三设备请求修改或锁定所述配置数据集。
  13. 根据权利要求12所述的第二设备，其特征在于，
    所述第一响应消息包括所述第三设备的信息；其中，所述第三设备的信息包括：所述第三设备的网际协议IP地址和所述第三设备的用户标识中的至少一个。
  14. 根据权利要求12或13所述的第二设备，其特征在于，所述发送单元还用于：
    当所述第二设备释放所述第一设备的数据集后，向所述第三设备发送通知消息，所述通知消息用于指示所述配置数据集已释放。
  15. 一种计算机可读存储介质，包括指令，其特征在于，当所述指令在计算机上运行时，使得计算机执行权利要求1至4任一项所述的网络管理方法。
  16. 一种计算机可读存储介质，包括指令，其特征在于，当所述指令在计算机上运行时，是的计算机执行权利要求5至7任一项所述的网络管理方法。
  17. 一种网络管理系统，其特征在于，该系统包括前述权利要求8至11所述的第一设备和前述权利要求12至14所述的第二设备。
PCT/CN2019/097562 2018-07-27 2019-07-24 一种网络管理方法和装置 Ceased WO2020020249A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP19841404.7A EP3823213B1 (en) 2018-07-27 2019-07-24 Network management method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810853147.3 2018-07-27
CN201810853147.3A CN110768818B (zh) 2018-07-27 2018-07-27 一种网络管理方法和装置

Publications (1)

Publication Number Publication Date
WO2020020249A1 true WO2020020249A1 (zh) 2020-01-30

Family

ID=69181327

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/097562 Ceased WO2020020249A1 (zh) 2018-07-27 2019-07-24 一种网络管理方法和装置

Country Status (3)

Country Link
EP (1) EP3823213B1 (zh)
CN (1) CN110768818B (zh)
WO (1) WO2020020249A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114006812A (zh) * 2021-10-30 2022-02-01 杭州迪普信息技术有限公司 网络设备的配置方法及装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112272104B (zh) * 2020-09-15 2023-06-30 浪潮思科网络科技有限公司 一种多形式配置管理的公共配置数据库方法及装置
CN116366438A (zh) * 2021-12-28 2023-06-30 华为技术有限公司 配置管理方法、装置、设备、系统、存储介质及程序产品
CN119892764B (zh) * 2024-12-05 2026-04-17 合肥锶矽网络科技有限公司 配置数据处理方法、装置、电子设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102148817A (zh) * 2010-12-08 2011-08-10 华为技术有限公司 配置网络设备的方法、客户端、服务器端及网络系统
US20150019991A1 (en) * 2013-07-09 2015-01-15 Tail-f Systems AB Customizable graphical user interface for network management
CN105979321A (zh) * 2016-04-29 2016-09-28 乐视控股（北京）有限公司 防止硬件资源占用冲突的方法及系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008014809A1 (de) * 2006-08-03 2008-02-07 Siemens Home And Office Communication Devices Gmbh & Co. Kg Vorrichtung und verfahren zur konfiguration von telekommunikationsendgeräten
CN101505248B (zh) * 2009-02-25 2012-04-04 成都市华为赛门铁克科技有限公司 一种监控锁定机制的方法及装置
CN105068945A (zh) * 2015-08-03 2015-11-18 Tcl集团股份有限公司 一种Android系统的摄像头分配方法及系统
CN106470115B (zh) * 2015-08-20 2021-01-29 斑马智行网络(香港)有限公司 一种安全配置方法、相关装置和系统
CN105959148A (zh) * 2016-06-15 2016-09-21 上海斐讯数据通信技术有限公司 一种网管系统控制网络设备的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102148817A (zh) * 2010-12-08 2011-08-10 华为技术有限公司 配置网络设备的方法、客户端、服务器端及网络系统
US20150019991A1 (en) * 2013-07-09 2015-01-15 Tail-f Systems AB Customizable graphical user interface for network management
CN105979321A (zh) * 2016-04-29 2016-09-28 乐视控股（北京）有限公司 防止硬件资源占用冲突的方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3823213A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114006812A (zh) * 2021-10-30 2022-02-01 杭州迪普信息技术有限公司 网络设备的配置方法及装置

Also Published As

Publication number Publication date
CN110768818B (zh) 2021-02-12
EP3823213B1 (en) 2026-01-28
EP3823213A4 (en) 2021-09-08
EP3823213A1 (en) 2021-05-19
CN110768818A (zh) 2020-02-07

Similar Documents

Publication Publication Date Title
US12382264B2 (en) Cross-resource subscription for M2M service layer
US11750702B2 (en) Subscription and notification service
EP3800934A1 (en) Method for routing internet of things service
US9743367B2 (en) Link layer discovery protocol (LLDP) on multiple nodes of a distributed fabric
EP2676411B1 (en) Method and system for classification and management of inter-blade network traffic in a blade server
US10313380B2 (en) System and method for centralized virtual interface card driver logging in a network environment
WO2021093782A1 (zh) 执行意图的方法及装置
WO2019047911A1 (zh) 一种物联网资源订阅的方法、设备和系统
CN110768818B (zh) 一种网络管理方法和装置
WO2021098819A1 (zh) 一种路由更新方法和用户集群
EP3885939A1 (en) Information query method, apparatus, device, and storage medium
CN112105026B (zh) 一种授权控制的方法、装置以及存储介质
US10268532B2 (en) Application message processing system, method, and application device
CN101729413B (zh) 基于atca的多业务处理系统及方法
Ahmad et al. Protection of centralized SDN control plane from high-rate Packet-In messages
CN110351107A (zh) 配置管理方法及装置
WO2022052496A1 (zh) 地址预留的方法、网络设备和系统
WO2021159706A1 (zh) 物联网终端的网络业务控制方法、装置和存储介质
WO2022228121A1 (zh) 提供服务的方法及装置
CN109905645A (zh) 视频监控设备目录交换方法和联网平台
CN115988078A (zh) 通信方法、系统、电子设备及存储介质
CN115665026A (zh) 一种集群组网的方法和装置
WO2022022313A1 (zh) 传输路由信息的方法、装置和通信系统
WO2022160304A1 (zh) 多用户识别卡特性信息的交互方法、装置及通信设备
US12476835B2 (en) Event subscription method, apparatus, and system

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: 19841404

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019841404

Country of ref document: EP

Effective date: 20210210

WWG Wipo information: grant in national office

Ref document number: 2019841404

Country of ref document: EP