Capability negotiation method, network controller and terminal device

Abstract

The present invention provides a capability negotiation method, a network controller, and a terminal device. The capability negotiation method comprises: sending a first message to a terminal device, the first message including an identifier of the network controller; and receiving a second message sent by the terminal device, the second message including a capability set supported by the terminal device corresponding to the identifier. The present invention can effectively reduce resource consumption of the network controller during the capability negotiation process and improve the efficiency of establishing a connection between the network controller and the terminal device.

Description

Technical Field

[0001] The embodiments of the present invention relate to the technical fields of transmission and IP (Internet Protocol), and in particular to a capability negotiation method, a network controller, and a terminal device. Background Art

[0002] SDWAN (Software-Defined Wide Area Network) controllers typically manage and control CPE (Customer Premise Equipment) using NETCONF (Network Configuration Protocol). This protocol distributes specific service configurations. Before distributing service configurations, the SDWAN controller and CPE must negotiate NETCONF capabilities to align their supported capabilities and ensure proper service delivery. Currently, capability negotiation is accomplished by the CPE directly sending HELLO messages after establishing a connection.

[0003] In actual inter-manufacturer docking, due to the different capabilities supported by each manufacturer, a large number of manufacturer-specific capabilities are reported during capability negotiation. As a result, the SDWAN controller cannot recognize the private capabilities, triggering repeated renegotiation and consuming the processing resources of the SDWAN controller. Summary of the Invention

[0004] An embodiment of the present invention provides a capability negotiation method, a network controller, and a terminal device, which are used to solve the problem that the SDWAN controller cannot recognize the private capabilities reported by the CPE, triggering repeated renegotiation and consuming the processing resources of the SDWAN controller.

[0005] In order to solve the above-mentioned technical problems, the present invention is achieved as follows:

[0006] In a first aspect, an embodiment of the present invention provides a capability negotiation method, applied to a network controller, comprising:

[0007] Sending a first message to a terminal device, where the first message includes an identifier of the network controller;

[0008] A second message sent by the terminal device is received, where the second message includes a capability set supported by the terminal device corresponding to the identifier.

[0009] Optionally, the first message and the second message are Hello messages in the NETCONF protocol.

[0010] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried through the factory field in the first message.

[0011] Optionally, the first message also includes a capability set supported by the network controller.

[0012] Optionally, the second message also includes the identifier.

[0013] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory-back field in the second message.

[0014] Optionally, after receiving the second message sent by the terminal device, the method further includes:

[0015] Obtain the capability set supported by the terminal device in the second message and compare it with the capability set supported by itself. If the comparison is successful, the capability negotiation process is completed.

[0016] Optionally, obtaining the capability set supported by the terminal device in the second message includes:

[0017] Determining whether the second message includes an identifier of the network controller;

[0018] If the second message does not include the identifier of the network controller, discard the second message;

[0019] If the second message contains the identifier of the network controller, obtain the capability set supported by the terminal device in the second message.

[0020] In a second aspect, an embodiment of the present invention provides a capability negotiation method, applied to a terminal device, including:

[0021] receiving a first message sent by a network controller, where the first message includes an identifier of the network controller;

[0022] Determining a capability set supported by the terminal device corresponding to the identifier;

[0023] A second message is sent to the network controller, where the second message includes a capability set supported by the terminal device corresponding to the identifier.

[0024] Optionally, the first message and the second message are Hello messages in the NETCONF protocol.

[0025] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried through the factory field in the first message.

[0026] Optionally, the first message further includes a capability set supported by the network controller;

[0027] Determining the capability set supported by the terminal device corresponding to the identifier includes:

[0028] extracting a capability set supported by the network controller from the first message;

[0029] The local capability set is traversed to determine a capability set that matches the capability set supported by the network controller, and the capability set is used as the capability set supported by the terminal device corresponding to the identifier.

[0030] Optionally, the second message also includes the identifier.

[0031] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory-back field in the second message.

[0032] In a third aspect, an embodiment of the present invention provides a network controller, including:

[0033] A sending module, configured to send a first message to a terminal device, where the first message includes an identifier of the network controller;

[0034] A receiving module is used to receive a second message sent by the terminal device, where the second message includes a capability set supported by the terminal device corresponding to the identifier.

[0035] Optionally, the first message and the second message are Hello messages in the NETCONF protocol.

[0036] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried through the factory field in the first message.

[0037] Optionally, the first message also includes a capability set supported by the network controller.

[0038] Optionally, the second message also includes the identifier.

[0039] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory-back field in the second message.

[0040] Optionally, the network controller further includes:

[0041] The processing module is used to obtain the capability set supported by the terminal device in the second message and compare it with the capability set supported by itself. If the comparison is successful, the capability negotiation process is completed.

[0042] Optionally, the processing module is used to determine whether the second message contains the identifier of the network controller; if the second message does not contain the identifier of the network controller, discard the second message; if the second message contains the identifier of the network controller, obtain the capability set supported by the terminal device in the second message.

[0043] In a fourth aspect, an embodiment of the present invention provides a network controller, comprising: a transceiver and a processor;

[0044] The transceiver is configured to send a first message to a terminal device, where the first message includes an identifier of the network controller;

[0045] The transceiver is further used to receive a second message sent by the terminal device, where the second message includes a capability set supported by the terminal device corresponding to the identifier.

[0046] Optionally, the second message also includes the identifier.

[0047] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory-back field in the second message.

[0048] In a fifth aspect, an embodiment of the present invention provides a terminal device, including:

[0049] A receiving module, configured to receive a first message sent by a network controller, where the first message includes an identifier of the network controller;

[0050] a determination module, configured to determine a capability set supported by the terminal device corresponding to the identifier;

[0051] A sending module is used to send a second message to the network controller, where the second message includes a capability set supported by the terminal device corresponding to the identifier.

[0052] Optionally, the first message and the second message are Hello messages in the NETCONF protocol.

[0053] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried through the factory field in the first message.

[0054] Optionally, the first message further includes a capability set supported by the network controller;

[0055] The determination module is used to extract the capability set supported by the network controller from the first message; traverse the local capability set and determine the capability set that matches the capability set supported by the network controller as the capability set supported by the terminal device corresponding to the identifier.

[0056] Optionally, the second message also includes the identifier.

[0057] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory-back field in the second message.

[0058] In a sixth aspect, an embodiment of the present invention provides a terminal device, including: a transceiver and a processor;

[0059] The transceiver is configured to receive a first message sent by a network controller, where the first message includes an identifier of the network controller;

[0060] The processor is configured to determine a capability set supported by the terminal device corresponding to the identifier;

[0061] The transceiver is further configured to send a second message to the network controller, where the second message includes a capability set supported by the terminal device corresponding to the identifier.

[0062] Optionally, the first message and the second message are Hello messages in the NETCONF protocol.

[0063] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried through the factory field in the first message.

[0064] Optionally, the first message further includes a capability set supported by the network controller;

[0065] The processor is used to extract the capability set supported by the network controller from the first message; traverse the local capability set, and determine the capability set that matches the capability set supported by the network controller as the capability set supported by the terminal device corresponding to the identifier.

[0066] Optionally, the second message also includes the identifier.

[0067] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory-back field in the second message.

[0068] In the seventh aspect, an embodiment of the present invention provides a network controller comprising: a processor, a memory, and a program stored on the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the capability negotiation method of the first aspect mentioned above.

[0069] In an eighth aspect, an embodiment of the present invention provides a terminal device comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the capability negotiation method of the second aspect described above.

[0070] In the ninth aspect, an embodiment of the present invention provides a computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, and when the computer program is executed by the processor, the steps of the capability negotiation method of the first aspect are implemented; or, when the computer program is executed by the processor, the steps of the capability negotiation method of the second aspect are implemented.

[0071] In an embodiment of the present invention, the capability set reported by the terminal to the network controller is a capability set that matches the identifier of the network controller. The network controller can identify the capability set reported by the terminal, thereby avoiding repeated negotiation problems in capability negotiation between the network controller and the terminal device, effectively reducing the resource consumption of the network controller during the capability negotiation process, and improving the connection efficiency between the network controller and the terminal device, thereby improving customer experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present invention. The same reference symbols are used throughout the drawings to represent the same components. In the drawings:

[0073] Figure 1 Schematic diagram of a flow chart of a capability negotiation method applied to a network controller according to an embodiment of the present invention;

[0074] Figure 2 Schematic diagram of a process flow of a capability negotiation method applied to a terminal device according to an embodiment of the present invention;

[0075] Figure 3 Schematic diagram of the interaction process of the capability negotiation process between SDWAN and CPE in an embodiment of the present invention;

[0076] Figure 4 This is a schematic structural diagram of an embodiment of the present invention applied to a network controller;

[0077] Figure 5 This is a schematic structural diagram of another embodiment of the present invention applied to a network controller;

[0078] Figure 6 This is a schematic structural diagram of an embodiment of the present invention applied to a terminal device;

[0079] Figure 7This is a schematic structural diagram of another embodiment of the present invention applied to a terminal device;

[0080] Figure 8 This is a structural diagram of a network controller according to another embodiment of the present invention;

[0081] Figure 9 This is a structural diagram of another embodiment of the present invention applied to a terminal device. DETAILED DESCRIPTION

[0082] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0083] Please refer to Figure 1 An embodiment of the present invention provides a capability negotiation method, applied to a network controller, comprising:

[0084] Step 11: Send a first message to the terminal device, where the first message includes an identifier of the network controller;

[0085] In the embodiment of the present invention, optionally, the identifier may be a manufacturer identifier of the network controller, such as the name of the network controller, or may be other types of identifiers.

[0086] The identifier can, on the one hand, enable the terminal to confirm that the message is a capability negotiation message, and on the other hand, enable the terminal to determine the capability set corresponding to the identifier and report it to the network controller.

[0087] Step 12: Receive a second message sent by the terminal device, where the second message includes a capability set supported by the terminal device corresponding to the identifier.

[0088] The network controller in the embodiment of the present invention may be an SDWAN (Software-Defined Wide Area Network) controller, and the terminal device may be a CPE (Customer Premise Equipment).

[0089] The SDWAN controller manages and controls CPEs through the NETCONF (Network Configuration Protocol) callhome mechanism, converting user operations into specific configurations and issuing them to the CPE to enable service provisioning. The CPE implements IPSEC (Internet Protocol Security) encryption and decryption, routing, link quality detection, and intelligent switching for SDWAN service traffic, providing high-speed wired and wireless access for end users.

[0090] The following briefly introduces the NETCONF protocol and the Callhome mechanism.

[0091] NETCONF protocol: Defined by RFC 6241, it replaces the command line interface (CLI), Simple Network Management Protocol (SNMP), and other proprietary configuration mechanisms. Management software can use NETCONF to write configuration data to devices and retrieve data from them. All data is encoded in Extensible Markup Language (XML) and transmitted using remote procedure calls (RPCs) over Secure Sockets Layer (SSL) or Transport Layer Security (TLS), a connection-oriented protocol.

[0092] Callhome mechanism: It is very helpful for the initial deployment and ongoing management of network devices. Its specific advantages are as follows:

[0093] 1) After the network device starts for the first time, it can actively call home to register with its management system.

[0094] 2) A network device can access the network in a manner in which an IP address is dynamically assigned, but does not register its assigned IP address with a mapping service (eg, dynamic DNS (Domain Name System)).

[0095] 3) Network devices can be deployed behind a firewall that implements Network Address Translation (NAT) for all internal network IP addresses.

[0096] 4) Network device elements can be deployed behind a firewall that does not allow any management access to the internal network.

[0097] Of course, it should be noted that in the embodiments of the present invention, it is not excluded that the network controller is other types of network controllers, and the terminal device is not excluded that the terminal device is other types of terminal devices.

[0098] In the above embodiment of the present invention, optionally, if the network controller and the terminal device communicate via the NETCONF protocol, the above step of sending the first message to the terminal device further includes: establishing a NETCONF connection with the terminal device.

[0099] In the embodiment of the present invention, if the network controller and the terminal device communicate via the NETCONF protocol, the network controller identifier may be carried by extending the NETCONF protocol.

[0100] In this embodiment of the present invention, optionally, the first message and the second message are Hello messages in the NETCONF protocol.

[0101] In the embodiment of the present invention, optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory field in the first message and may have the following format:

[0102] <capability>

[0103] urn:ietf:params:netconf:factory: <cotroller-name>

[0104] < / cotroller-name> < / capability>

[0105] in, <cotroller-name>is the name (ie, identifier) ​​of the network controller.

[0106] That is, a factory field is added to the first message to carry the identifier of the network controller.

[0107] In the embodiment of the present invention, optionally, the first message further includes a capability set supported by the network controller.

[0108] In an embodiment of the present invention, optionally, the second message also includes the identifier, through which the network controller can verify whether the message is a capability negotiation reply message. In addition, it can also verify whether the identifier carried in the second message is the identifier of the network controller, thereby verifying whether the second message belongs to itself.

[0109] In the embodiment of the present invention, optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory-back field in the second message and may have the following format:

[0110] <capability>

[0111] urn:ietf:params:netconf:factory-back: <cotroller-name>

[0112] < / cotroller-name> < / capability>

[0113] in, <cotroller-name>is the name (ie, identifier) ​​of the network controller.

[0114] That is, a factory-back field is added to the second message to carry the identifier of the network controller.

[0115] In the embodiment of the present invention, optionally, after receiving the second message sent by the terminal device, the method further includes:

[0116] Obtain the capability set supported by the terminal device in the second message and compare it with the capability set supported by itself. If the comparison is successful, the capability negotiation process is completed.

[0117] In the embodiment of the present invention, further optionally, obtaining the capability set supported by the terminal device in the second message includes:

[0118] Determining whether the second message includes an identifier of the network controller;

[0119] If the second message does not contain the identifier of the network controller, the second message is discarded; optionally, if the second message does not contain the identifier or does not contain the identifier of the network controller, both are discarded.

[0120] If the second message contains the identifier of the network controller, obtain the capability set supported by the terminal device in the second message.

[0121] That is to say, the network controller can decide whether to process the second message based on whether the second message contains the identifier of the network controller. It only processes the available second messages and directly discards the second messages that do not contain the identifier of the network controller, thereby improving processing efficiency.

[0122] Through the method in the embodiment of the present invention, the capability set reported by the terminal to the network controller is a capability set that matches the identifier of the network controller. The network controller can identify the capability set reported by the terminal, avoiding repeated negotiation problems in capability negotiation between the network controller and the terminal device, effectively reducing the resource consumption of the network controller during the capability negotiation process, and improving the connection efficiency between the network controller and the terminal device, thereby improving customer experience.

[0123] Please refer to Figure 2 The embodiment of the present invention further provides a capability negotiation method, applied to a terminal device, comprising:

[0124] Step 21: Receive a first message sent by a network controller, where the first message includes an identifier of the network controller;

[0125] The identifier can, on the one hand, enable the terminal to confirm that the message is a capability negotiation message, and on the other hand, enable the terminal to determine the capability set corresponding to the identifier and report it to the network controller.

[0126] Step 22: Determine a capability set supported by the terminal device corresponding to the identifier;

[0127] Step 23: Send a second message to the network controller, where the second message includes a capability set supported by the terminal device corresponding to the identifier.

[0128] Through the identifier in the first message, the terminal device can identify what type of network controller it is about to connect to, and thus can provide a capability set that matches this type of network controller. On the one hand, this can avoid the network controller being unable to identify the capability set reported by the terminal device, and on the other hand, it can also avoid unnecessary overhead caused by reporting the entire capability set.

[0129] The network controller in the embodiment of the present invention may be an SDWAN controller, and the terminal device may be a CPE.

[0130] In the embodiment of the present invention, if the network controller and the terminal device communicate via the NETCONF protocol, the network controller identifier may be carried by extending the NETCONF protocol.

[0131] In this embodiment of the present invention, optionally, the first message and the second message are Hello messages in the NETCONF protocol.

[0132] In the embodiment of the present invention, optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory field in the first message.

[0133] In an embodiment of the present invention, optionally, the first message further includes a capability set supported by the network controller; and determining the capability set supported by the terminal device corresponding to the identifier includes:

[0134] extracting a capability set supported by the network controller from the first message;

[0135] The local capability set is traversed to determine a capability set that matches the capability set supported by the network controller, and the capability set is used as the capability set supported by the terminal device corresponding to the identifier.

[0136] In this embodiment of the present invention, the second message optionally further includes the identifier. Using the identifier, the network controller can verify whether the message is a capability negotiation reply message. Furthermore, the network controller can verify whether the identifier carried in the second message is the identifier of the network controller, thereby verifying whether the second message belongs to itself.

[0137] In the embodiment of the present invention, optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory-back field in the second message.

[0138] The capability negotiation method of an embodiment of the present invention is described below by taking the network controller as an SDWAN controller and the terminal device as a CPE as an example.

[0139] Please refer to Figure 3 The capability negotiation method of an embodiment of the present invention includes:

[0140] Step 31: After the SDWAN controller successfully establishes a NETCONF connection, it sends a Hello message to the terminal device through NETCONF. The Hello message contains the factory field, which carries the SDWAN controller's manufacturer identifier. The Hello message also carries the capability set supported by the controller.

[0141] Step 32: After receiving the Hello message sent by the SDWAN controller, the CPE extracts the capability set supported by the SDWAN controller from the Hello message, and traverses the local capability set to find the capability set supported by the CPE that matches the capability set supported by the SDWAN controller.

[0142] Step 33: The CPE constructs a Hello message containing the factory-back field, which carries the vendor ID of the SDWAN controller. The CPE also carries the capability set it found to support, and sends the constructed Hello message to the network controller via NETCONF.

[0143] Step 34: After the SDWAN controller receives the Hello message sent by the CPE, it determines whether the received Hello message contains the manufacturer identifier of the SDWAN controller. If so, it extracts the capability set supported by the CPE from the received Hello message and compares the extracted capability set supported by the CPE with its own capability set. After the complete comparison is successful, the capability negotiation process is completed.

[0144] Please refer to Figure 4 , an embodiment of the present invention provides a network controller 40, including:

[0145] A sending module 41 is configured to send a first message to a terminal device, where the first message includes an identifier of the network controller;

[0146] The receiving module 42 is configured to receive a second message sent by the terminal device, where the second message includes a capability set supported by the terminal device corresponding to the identifier.

[0147] Optionally, the first message and the second message are Hello messages in the NETCONF protocol.

[0148] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried through the factory field in the first message.

[0149] Optionally, the first message also includes a capability set supported by the network controller.

[0150] Optionally, the second message also includes the identifier.

[0151] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory-back field in the second message.

[0152] Optionally, the network controller further includes:

[0153] The processing module is used to obtain the capability set supported by the terminal device in the second message and compare it with the capability set supported by itself. If the comparison is successful, the capability negotiation process is completed.

[0154] Optionally, the processing module is used to determine whether the second message contains the identifier of the network controller; if the second message does not contain the identifier of the network controller, discard the second message; if the second message contains the identifier of the network controller, obtain the capability set supported by the terminal device in the second message.

[0155] Please refer to Figure 5 , an embodiment of the present invention provides a network controller 50, comprising: a transceiver 51 and a processor 52;

[0156] The transceiver 51 is configured to send a first message to a terminal device, where the first message includes an identifier of the network controller;

[0157] The transceiver 51 is further configured to receive a second message sent by the terminal device, where the second message includes a capability set supported by the terminal device corresponding to the identifier.

[0158] Optionally, the second message also includes the identifier.

[0159] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory-back field in the second message.

[0160] Please refer to Figure 6 , an embodiment of the present invention provides a terminal device 60, including:

[0161] A receiving module 61 is configured to receive a first message sent by a network controller, where the first message includes an identifier of the network controller;

[0162] A determination module 62, configured to determine a capability set supported by the terminal device corresponding to the identifier;

[0163] The sending module 63 is configured to send a second message to the network controller, where the second message includes a capability set supported by the terminal device corresponding to the identifier.

[0164] Optionally, the first message and the second message are Hello messages in the NETCONF protocol.

[0165] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried through the factory field in the first message.

[0166] Optionally, the first message further includes a capability set supported by the network controller;

[0167] The determination module 62 is used to extract the capability set supported by the network controller from the first message; traverse the local capability set and determine the capability set that matches the capability set supported by the network controller as the capability set supported by the terminal device corresponding to the identifier.

[0168] Optionally, the second message also includes the identifier.

[0169] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory-back field in the second message.

[0170] Please refer to Figure 7 , an embodiment of the present invention provides a terminal device 70, including: a transceiver 71 and a processor 72;

[0171] The transceiver 71 is configured to receive a first message sent by a network controller, where the first message includes an identifier of the network controller;

[0172] The processor 72 is configured to determine a capability set supported by the terminal device corresponding to the identifier;

[0173] The transceiver 71 is further configured to send a second message to the network controller, where the second message includes a capability set supported by the terminal device corresponding to the identifier.

[0174] Optionally, the first message and the second message are Hello messages in the NETCONF protocol.

[0175] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried through the factory field in the first message.

[0176] Optionally, the first message further includes a capability set supported by the network controller;

[0177] The processor 72 is used to extract the capability set supported by the network controller from the first message; traverse the local capability set, and determine the capability set that matches the capability set supported by the network controller as the capability set supported by the terminal device corresponding to the identifier.

[0178] Optionally, the second message also includes the identifier.

[0179] Optionally, the identifier is the manufacturer identifier of the network controller, which is carried by the factory-back field in the second message.

[0180] Please refer to Figure 8 An embodiment of the present invention provides a network controller 80, comprising: a processor 81, a memory 82, and a program stored in the memory 82 and executable on the processor. When the program is executed by the processor 81, the various processes of the above-mentioned embodiment of the capability negotiation method applied to the network controller are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0181] Please refer to Figure 9 An embodiment of the present invention provides a terminal device 90, including: a processor 91, a memory 92, and a program stored in the memory 92 and executable on the processor 91. When the program is executed by the processor 91, the various processes of the above-mentioned embodiment of the capability negotiation method applied to the terminal device are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0182] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the various processes of the embodiment of the capability negotiation method applied to the network controller, or, when executed by a processor, implements the various processes of the embodiment of the capability negotiation method applied to the terminal device, and can achieve the same technical effect. To avoid repetition, the details are not described here. The computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0183] It should be noted that, in this document, the terms "comprise," "include," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a..." does not preclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0184] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better embodiment. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0185] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are protected by the present invention.

Claims

1. A capability negotiation method, applied to a network controller, characterized in that: include: Sending a first message to the terminal device to implement control over the terminal device through a Callhome mechanism of a network configuration protocol, wherein the first message includes an identifier of the network controller, which is a manufacturer identifier of the network controller and is carried by a factory field in the first message; receiving a second message sent by the terminal device, where the second message includes a capability set supported by the terminal device corresponding to the identifier; the second message further includes the identifier, which is the manufacturer identifier of the network controller and is carried by a factory-back field in the second message; The first message and the second message are Hello messages in the NETCONF protocol.

2. The method according to claim 1, characterized in that The first message also includes a capability set supported by the network controller.

3. The method according to claim 1, characterized in that After receiving the second message sent by the terminal device, the method further includes: Obtain the capability set supported by the terminal device in the second message and compare it with the capability set supported by itself. If the comparison is successful, the capability negotiation process is completed.

4. The method according to claim 3, characterized in that Obtaining the capability set supported by the terminal device in the second message includes: Determining whether the second message includes an identifier of the network controller; If the second message does not include the identifier of the network controller, discard the second message; If the second message contains the identifier of the network controller, obtain the capability set supported by the terminal device in the second message.

5. A capability negotiation method, applied to a terminal device, characterized in that: include: receiving a first message sent by a network controller, and implementing control over the terminal device through a Callhome mechanism of a network configuration protocol, wherein the first message includes an identifier of the network controller, where the identifier is a manufacturer identifier of the network controller and is carried by a factory field in the first message; Determining a capability set supported by the terminal device corresponding to the identifier; Sending a second message to the network controller, where the second message includes a capability set supported by the terminal device corresponding to the identifier; the second message also includes the identifier, which is the manufacturer identifier of the network controller and is carried by the factory-back field in the second message; The first message and the second message are Hello messages in the NETCONF protocol.

6. The method according to claim 5, characterized in that The first message also includes a capability set supported by the network controller; Determining the capability set supported by the terminal device corresponding to the identifier includes: extracting a capability set supported by the network controller from the first message; The local capability set is traversed to determine a capability set that matches the capability set supported by the network controller, and the capability set is used as the capability set supported by the terminal device corresponding to the identifier.

7. A network controller, characterized in that: include: a sending module, configured to send a first message to a terminal device to implement control over the terminal device through a Callhome mechanism of a network configuration protocol, wherein the first message includes an identifier of the network controller, which is a manufacturer identifier of the network controller and is carried by a factory field in the first message; a receiving module, configured to receive a second message sent by the terminal device, the second message including a capability set supported by the terminal device corresponding to the identifier; the second message further including the identifier, which is a manufacturer identifier of the network controller and is carried by a factory-back field in the second message; The first message and the second message are Hello messages in the NETCONF protocol.

8. A network controller, characterized in that: include: transceivers and processors; The transceiver is configured to send a first message to the terminal device to implement control over the terminal device through a Callhome mechanism of a network configuration protocol, wherein the first message includes an identifier of the network controller, which is a manufacturer identifier of the network controller and is carried by a factory field in the first message; The transceiver is also used to receive a second message sent by the terminal device, wherein the second message includes a capability set supported by the terminal device corresponding to the identifier; the second message also includes the identifier, which is the manufacturer identifier of the network controller and is carried by the factory-back field in the second message; the first message and the second message are Hello messages in the NETCONF protocol.

9. A terminal device, characterized in that: include: a receiving module, configured to receive a first message sent by a network controller, and implement control over a terminal device through a Callhome mechanism of a network configuration protocol, wherein the first message includes an identifier of the network controller, which is a manufacturer identifier of the network controller and is carried by a factory field in the first message; a determination module, configured to determine a capability set supported by the terminal device corresponding to the identifier; A sending module is used to send a second message to the network controller, wherein the second message includes a capability set supported by the terminal device corresponding to the identifier; the second message also includes the identifier, which is the manufacturer identifier of the network controller and is carried by the factory-back field in the second message; the first message and the second message are Hello messages in the NETCONF protocol.

10. A terminal device, characterized in that: include: transceivers and processors; The transceiver is configured to receive a first message sent by a network controller, and implement control over the terminal device through a Callhome mechanism of a network configuration protocol, wherein the first message includes an identifier of the network controller, which is a manufacturer identifier of the network controller and is carried by a factory field in the first message; The processor is configured to determine a capability set supported by the terminal device corresponding to the identifier; The transceiver is also used to send a second message to the network controller, wherein the second message includes a capability set supported by the terminal device corresponding to the identifier; the second message also includes the identifier, which is the manufacturer identifier of the network controller and is carried by the factory-back field in the second message; the first message and the second message are Hello messages in the NETCONF protocol.

11. A network controller, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the capability negotiation method according to any one of claims 1 to 4 are implemented.

12. A terminal device, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the capability negotiation method according to any one of claims 5 or 6 are implemented.

13. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, it implements the steps of the capability negotiation method according to any one of claims 1 to 4; or, when the computer program is executed by the processor, it implements the steps of the capability negotiation method according to any one of claims 5 or 6.

Images