Netconf-based communication method and apparatus, computing device and storage medium

Abstract

The present disclosure relates to an NETCONF-based communication method and apparatus, a computing device and a storage medium. The NETCONF-based communication method is executed on a management device, and comprises: the management device establishes a standard NETCONF session with managed devices; the management device creates a group for the managed devices; the management device sends a group configuration parameter to the managed devices by means of the standard NETCONF session, so that the managed devices join the group; the management device sends a multicast request message to the group; and the management device receives response messages from the managed devices by means of the standard NETCONF session.

Description

NETCONF-based communication method, device, computing device, and storage medium Technical Field

[0001] The present disclosure generally relates to the field of network technology, and more particularly to a NETCONF-based communication method, apparatus, computing device, and storage medium. Background Art

[0002] The NETCONF protocol is widely used when a management device configures and manages managed devices over the network. NETCONF is connection-oriented, and each NETCONF session is based on a TCP connection. The management device acts as a NETCONF client, while each managed device runs a NETCONF server. When a NETCONF client manages a large number of devices, if the client wants to obtain information from a group of managed devices, it must send the same Remote Procedure Call (RPC) request message to each managed device separately, which reduces communication efficiency.

[0003] According to the NETCONF protocol, the standard method for a client to operate a group of managed devices is that the client communicates with each device using the unicast IP address of each device.

[0004] Summary of the Invention

[0005] A brief overview of the present invention is provided below to provide a basic understanding of certain aspects of the present invention. It should be understood that this overview is not an exhaustive overview of the present invention. It is not intended to identify key or important aspects of the present invention, nor is it intended to limit the scope of the present invention. Its purpose is simply to present certain concepts in a simplified form as a prelude to the more detailed description discussed later.

[0006] In view of this, the present disclosure provides a communication method based on NETCONF. By grouping the managed devices, the communication from the management device to the managed devices can be changed from unicast communication to multicast communication. The management device does not need to send request messages to the unicast address of each managed device separately, but only needs to send a multicast request message once, and all managed devices in the group can receive the multicast request message.

[0007] According to one aspect of the present disclosure, a NETCONF-based communication method is provided. The method is executed on a management device and includes:

[0008] The management device establishes a standard NETCONF session with the managed device.

[0009] The management device creates a group for the managed device;

[0010] The management device sends group configuration parameters to the managed device through a standard NETCONF session so that the managed device joins the group;

[0011] The management device sends a multicast request message to the group;

[0012] The management device receives a response message from the managed device through the standard NETCONF session.

[0013] In this way, the management device does not need to send request messages to the unicast addresses of each managed device respectively, but only needs to send a multicast request message once, and all managed devices in the group can receive the multicast request message.

[0014] Optionally, in an example of the above aspect, the group configuration parameter includes at least one of the following: a management device IP address, a multicast IP address, a multicast listening port number, and an encryption key.

[0015] In this way, multicast groups can be established and the security of communications can be improved by using encryption keys.

[0016] Optionally, in an example of the above aspect, the method further includes: the management device sending a new group configuration message to the managed device through a standard NETCONF session, and after receiving a correct response message, moving the managed device to a new group.

[0017] In this way, the managed devices can be changed into new groups.

[0018] Optionally, in an example of the above aspect, the method further includes:

[0019] The management device sends a removal request to the managed device through a standard NETCONF session, and deletes the managed device from the group after receiving a confirmation message from the managed device.

[0020] In this way, a managed device can be deleted from a group.

[0021] Optionally, in an example of the above aspect, the method further includes:

[0022] The management device sends a delete group message to the group, and deletes the group after receiving confirmation messages from all managed devices.

[0023] In this way, a group can be deleted.

[0024] According to another aspect of the present disclosure, a NETCONF-based communication method is provided, the method being executed on a managed device and comprising:

[0025] Establish a standard NETCONF session between the managed device and the management device.

[0026] The managed device receives the group configuration parameters from the management device;

[0027] The managed device joins the corresponding group according to the group configuration parameters, receives the multicast request message from the management device, and decodes it;

[0028] The managed device sends a response message to the management device through the standard NETCONF session in response to the decoded multicast request message.

[0029] According to another aspect of the present disclosure, a NETCONF-based communication method is provided, including:

[0030] The management device and the managed device establish a standard NETCONF session.

[0031] The management device creates a group for the managed device;

[0032] The management device sends group configuration parameters to the managed device through a standard NETCONF session;

[0033] The managed device that receives the group configuration parameters joins the group;

[0034] When the management device wants to obtain information from a group of managed devices, the management device sends a multicast request message to the group;

[0035] All managed devices receive the multicast request message from the management device and decode it; and

[0036] The managed device sends a response message to the management device through the standard NETCONF session.

[0037] According to another aspect of the present disclosure, a NETCONF-based communication apparatus is provided, wherein the communication apparatus is provided on a management device and includes:

[0038] A standard session establishing unit, configured to establish a standard NETCONF session with a managed device;

[0039] a group creating unit, configured to create a group for the managed device;

[0040] a group configuration parameter sending unit, configured to send group configuration parameters to the managed device through a standard NETCONF session so that the managed device joins the group;

[0041] an acceleration unit, configured to send a multicast request message to the group; and

[0042] The response message receiving unit is configured to receive a response message from the managed device through the standard NETCONF session.

[0043] According to another aspect of the present disclosure, a NETCONF-based communication device (600) is provided, wherein the communication device is provided on a managed device and includes:

[0044] A standard session establishing unit is configured to establish a standard NETCONF session between the managed device and the management device;

[0045] a group configuration parameter sending unit, configured to receive group configuration parameters from a management device;

[0046] an acceleration unit configured to enable the managed device to join a corresponding group according to the group configuration parameters, receive a multicast request message from the management device, and decode the multicast message;

[0047] The response message sending unit is configured to reply a response message to the management device through the standard NETCONF session in response to the decoded multicast request message.

[0048] According to another aspect of the present disclosure, a computing device is provided, comprising: at least one processor; and a memory coupled to the at least one processor, the memory being configured to store instructions that, when executed by the at least one processor, enable the processor to perform the method described above.

[0049] According to another aspect of the present disclosure, a non-transitory machine-readable storage medium is provided, which stores executable instructions. When the instructions are executed, the machine is caused to perform the method described above.

[0050] According to another aspect of the present disclosure, a computer program product is provided, which is tangibly stored on a computer-readable medium and includes computer-executable instructions that, when executed, cause at least one processor to perform the method described above.

[0051] Using the method and apparatus of the present invention, some communications from a management device to managed devices are changed from unicast to multicast. A managed device only needs to send a request once, and all managed devices in the same group can receive it. This reduces network traffic and improves communication efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The above and other purposes, features and advantages of the present invention will be more easily understood by referring to the following description of the embodiments of the present invention in conjunction with the accompanying drawings. The components in the accompanying drawings are only for illustrating the principles of the present invention. In the accompanying drawings, the same or similar technical features or components will be represented by the same or similar reference numerals. In the accompanying drawings:

[0053] FIG1 is a schematic diagram of a communication system that performs communication using a communication method based on the NETCONF protocol according to an embodiment of the present disclosure;

[0054] FIG2 is a flowchart of an exemplary process of a communication method based on the NETCONF protocol according to an embodiment of the present disclosure;

[0055] FIG3 is a flowchart of an exemplary process of a communication method performed at a management device according to an embodiment of the present disclosure;

[0056] FIG4 is a flowchart of an exemplary process of a communication method performed at a managed device according to an embodiment of the present disclosure;

[0057] 5 is a block diagram of an exemplary configuration of a communication device for executing the communication method shown in FIG. 3 ;

[0058] FIG6 is a block diagram of an exemplary configuration of a communication device for executing the communication method shown in FIG4;

[0059] FIG7 shows a block diagram of a computing device according to an embodiment of the present disclosure.

[0060] Wherein, the reference numerals are as follows: 10: communication system 102: NETCONF client 104: NETCONF server 1022, 1042: accelerator module 106: packets 200, 300, 400: communication methods S202, S204, S206, S208, S210, S302, S304, S306, S308, S310, S212, S214, S216, S218, S220: S312, S314, S316, S402, S404, Steps S406, S408: Steps 500, 600: Communication device 502: Standard session establishment unit 504: Group creation unit 506: Group configuration parameter sending unit 508: Acceleration unit 510: Response message receiving unit 602: Standard session establishment unit 604: Group configuration parameter receiving unit 606: Acceleration unit 608: Response message sending unit 700: Computing device 702: Processor 704: Memory DETAILED DESCRIPTION

[0061] The subject matter described herein will now be discussed with reference to example embodiments. It should be understood that discussing these embodiments is intended only to enable those skilled in the art to better understand and implement the subject matter described herein, and is not intended to limit the scope of protection, applicability, or examples set forth in the claims. The functions and arrangements of the elements discussed may be changed without departing from the scope of protection of this disclosure. Various examples may omit, replace, or add various processes or components as needed. For example, the described method may be performed in an order different from the described order, and various steps may be added, omitted, or combined. In addition, features described relative to some examples may also be combined in other examples.

[0062] As used herein, the term "including" and its variations are open terms meaning "including but not limited to". The term "based on" means "based at least in part on". The terms "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other definitions may be included below, whether explicit or implicit. Unless the context clearly indicates otherwise, the definition of a term is consistent throughout the specification.

[0063] As described above, in a system based on NETCONF protocol communication, a management device communicates with each managed device using the unicast IP address of each managed device, resulting in low communication efficiency.

[0064] In view of this, the present disclosure provides a communication method based on NETCONF. By grouping the managed devices, the communication from the management device to the managed devices can be changed from unicast communication to multicast communication. The management device does not need to send request messages to the unicast address of each managed device separately, but only needs to send a multicast request message once, and all managed devices in the group can receive the multicast request message.

[0065] The management device and managed devices that communicate using the NETCONF protocol are also referred to as the NETCONF client and NETCONF server, respectively. In this document, the management device is equivalent to the NETCONF client, and the managed device is equivalent to the NETCONF server.

[0066] When using the NETCONF protocol for communication, messages sent from the client to the server are "RPC" messages, and messages sent from the server to the client are "RPC-reply" messages.

[0067] The following describes a communication method and apparatus based on the NETCONF protocol according to an embodiment of the present disclosure with reference to the accompanying drawings.

[0068] FIG1 is a schematic diagram of a communication system 10 that performs communication using a communication method based on the NETCONF protocol according to an embodiment of the present disclosure.

[0069] The communication system 10 includes a NETCONF client 102 and a plurality of NETCONF servers 104 .

[0070] To implement the communication method according to the embodiment of the present disclosure, in a specific embodiment, the management device 102 adds an accelerator module 1022 , and the managed device 104 adds an accelerator module 1042 .

[0071] The accelerator module 1042 on the managed device 104 side can receive multicast messages and can be pre-configured through a standard NETCONF session.

[0072] Initially, the accelerator modules are disabled, and communication between the management device 102 and the managed devices 104 occurs via standard NETCONF. After the managed devices 104 are grouped, their accelerator modules 1042 are activated and join the configured multicast group 106. When the management device 102 wishes to obtain data from a group of managed devices 104, it can send a request to the multicast address of the corresponding group 106 via its accelerator module 1022. Upon receiving the request, the managed device 104 sends the requested data to the management device using an RPC reply over the existing NETCONF session.

[0073] Those skilled in the art will appreciate that the address of the multicast group 106 is, for example, a multicast IP address, and the multicast message sent by the management device is forwarded via a gateway or a switch, which will not be described in detail here.

[0074] FIG2 is a flowchart of an exemplary process of a communication method 200 based on the NETCONF protocol according to an embodiment of the present disclosure.

[0075] First, in block S202 of FIG. 2 , the management device and the managed device establish a standard NETCONF session.

[0076] Next, in block S204 , the management device creates a group for the managed devices.

[0077] In block S206 , the management device sends group configuration parameters to the managed device through a standard NETCONF session.

[0078] The group configuration parameters may specifically include: management device IP address, multicast IP address, multicast listening port number, encryption key, etc.

[0079] It's understood that standard NETCONF sessions use TCP to ensure communication security. However, the communication method disclosed herein groups managed devices and then performs multicast communication over UDP, which can compromise communication security. The management device sends encryption keys to managed devices, which can then be used to encrypt data in subsequent communications, ensuring communication security.

[0080] In block S208 , the managed device that receives the group configuration parameters joins the group.

[0081] Specifically, the managed device may provide group configuration parameters to the accelerator module included therein and activate the accelerator module; then the accelerator module on the managed device joins a specific group through IGMP and waits for receiving a message of the group.

[0082] In block S210 , when the management device wants to obtain information from a group of managed devices, the management device sends a multicast request message to the group.

[0083] Specifically, the accelerator module of the management device may send a multicast request message to the corresponding multicast address according to a predetermined message format.

[0084] In block S212 , the managed device receives and decodes the multicast request message from the management device.

[0085] Specifically, the accelerator module of the managed device may perform decoding, and then the accelerator module forwards the decoded request message to the managed device.

[0086] Finally, in block S214 , the managed device sends a response message to the management device through a standard NETCONF session.

[0087] The response message is a message in the "RPC-reply" format.

[0088] That is, when a management device wants to obtain data from a group of managed devices, it can send a request message to the corresponding multicast address. All managed devices in the group can receive the message and then send response messages to the management device through a standard NETCONF session.

[0089] In one example, when the management device wants to change a managed device to another group, the communication method 200 may also include the operation in box S216: the management device sends a new group configuration message in the form of RPC to the managed device through a standard NETCONF session, the accelerator module of the managed device sends an IGMP leave message to the current group, and sends an IGMP join message to the new group, and after the management device receives the correct reply message (RPC-reply), the managed device is moved to the new group.

[0090] The new group configuration message may include the management device IP address, a new multicast IP address, a new multicast listening port number, a new encryption key, and the like.

[0091] In one example, when the management device wants to remove some managed devices from the group, the communication method 200 may also include the operation in box S218: the management device sends a removal request in the form of RPC to the managed device through a standard NETCONF session, the accelerator module of the managed device sends an IGMP leave message to the current group, disables the accelerator module, and then the managed device sends a reply message (RPC-reply) to the management device to confirm the operation, and the management device deletes the managed device from the group.

[0092] In one example, when the management device wants to delete a group, the communication method 200 may also include the operation in box S220: the management device sends a multicast message to delete the group through the accelerator module, and all managed devices receive the message. After the managed devices receive the message, the accelerator module sends an IGMP leave message, the accelerator module is disabled, and the managed devices send a response message to the management device to confirm the operation. After the management device receives the confirmation messages from all managed devices, it deletes the group.

[0093] In the above specific embodiment, an accelerator module is added to the management device and the managed device respectively to perform operations related to sending multicast. It can be understood that this is only a specific software implementation of the communication method according to the embodiment of the present disclosure, and the specific implementation of the communication method according to the present disclosure is not limited to this.

[0094] In the NETCONF protocol-based communication method according to an embodiment of the present disclosure shown in FIG2 , two aspects are involved: a management device and a managed device. For the management device, the operation steps performed are shown in FIG3 . FIG3 is a flowchart of an exemplary process of a communication method 300 performed at a management device according to an embodiment of the present disclosure, and the method specifically includes:

[0095] In block S302 , the management device and the managed device establish a standard NETCONF session;

[0096] In block S304, the management device creates a group for the managed device;

[0097] In block S306, the management device sends group configuration parameters to the managed device through a standard NETCONF session so that the managed device joins the group;

[0098] In block S308, the management device sends a multicast request message to the group;

[0099] In block S310 , the management device receives a response message from the managed device through the standard NETCONF session.

[0100] In one example, the communication method 300 may further include the operation in block S312: the management device sends a new group configuration message to the managed device through a standard NETCONF session, and after receiving a correct response message, moves the managed device to the new group.

[0101] Through the operation in S312 , the grouping of a managed device can be changed on the management device side.

[0102] In another example, the communication method 300 may further include the operation in block S314: the management device sends a removal request to the managed device through a standard NETCONF session, and after receiving a confirmation message from the managed device, deletes the managed device from the group.

[0103] Through the operation in S314 , a managed device can be deleted from the group on the management device side.

[0104] In another example, the communication method 300 may further include the operation in block S316: the management device sends a delete group message to the group, and deletes the group after receiving confirmation messages from all managed devices.

[0105] Through the operation in S316, a group can be deleted on the management device side.

[0106] The above description uses FIG3 to illustrate the operation steps performed by the management device during the communication between the management device and the managed device using the communication method according to an embodiment of the present disclosure. The operation steps performed by the managed device are shown in FIG4. FIG4 is a flowchart of an exemplary process of a communication method 400 performed at a managed device according to an embodiment of the present disclosure. The method specifically includes:

[0107] In block S402 , the managed device and the management device establish a standard NETCONF session.

[0108] In block S404 , group configuration parameters are received from a management device.

[0109] In block S406 , the corresponding group is joined according to the group configuration parameters, and a multicast request message from the management device is received and decoded.

[0110] In block S408 , a response message is sent to the management device via the standard NETCONF session in response to the decoded multicast request message.

[0111] The managed device side may respectively perform operations corresponding to operations S312, S314, and S316 performed on the management device side to change the grouping of managed devices, delete a managed device from a group, and delete a group, which will not be described in detail here.

[0112] FIG5 is a block diagram showing an exemplary configuration of a communication device 500 for executing the communication method shown in FIG3 .

[0113] The communication device 500 includes a standard session establishing unit 502 , a group creating unit 504 , a group configuration parameter sending unit 506 , an acceleration unit 508 , and a response message receiving unit 510 .

[0114] The standard session establishing unit 502 is configured to establish a standard NETCONF session with the managed device.

[0115] The group creating unit 504 is configured to create a group for the managed device.

[0116] The group configuration parameter sending unit 506 is configured to send the group configuration parameters to the managed device through a standard NETCONF session so that the managed device joins the group.

[0117] The acceleration unit 508 is configured to send a multicast request message to the group.

[0118] The response message receiving unit 510 is configured to receive a response message from the managed device through the standard NETCONF session.

[0119] Optionally, the communication apparatus 500 further includes a group changing unit 512 configured to send a new group configuration message to the managed device through a standard NETCONF session, and move the managed device to the new group after receiving a correct response message.

[0120] Optionally, the communication apparatus 500 further includes a managed device deleting unit 514 configured to send a removal request to the managed device through a standard NETCONF session, and delete the managed device from the group after receiving a confirmation message from the managed device.

[0121] Optionally, the communication apparatus 500 further includes a group deleting unit 516 configured to send a group deletion message to the group, and delete the group after receiving confirmation messages from all managed devices.

[0122] FIG. 6 is a block diagram showing an exemplary configuration of a communication device 600 for executing the communication method shown in FIG. 4 .

[0123] The communication device 600 includes a standard session establishing unit 602 , a group configuration parameter receiving unit 604 , an acceleration unit 606 and a response message sending unit 608 .

[0124] The standard session establishing unit 602 is configured to establish a standard NETCONF session between the managed device and the management device.

[0125] The group configuration parameter receiving unit 604 is configured to receive group configuration parameters from a management device.

[0126] The acceleration unit 606 is configured to enable the managed device to join the corresponding group according to the group configuration parameters, receive a multicast request message from the management device, and decode the multicast message.

[0127] The response message sending unit 608 is configured to reply a response message to the management device through the standard NETCONF session in response to the decoded multicast request message.

[0128] It should be noted that the structures of the communication device 500 shown in FIG5 and the communication device 600 shown in FIG6 and their constituent units are merely exemplary, and those skilled in the art may modify the structural block diagrams shown in FIG5 and FIG6 as needed.

[0129] The details of the operations and functions of the various parts of the communication device 500 and the communication device 600 may be the same as or similar to the relevant parts of the embodiment of the NETCONF-based communication method of the present disclosure described in conjunction with Figures 1-4, and will not be described in detail here.

[0130] The method and apparatus according to the present disclosure have at least the following advantages:

[0131] The method and apparatus according to the embodiments of the present disclosure are described above with reference to Figures 1 to 6. Each unit of the robot simulation apparatus described above can be implemented using hardware, software, or a combination of hardware and software.

[0132] 7 shows a block diagram of a computing device 700 according to an embodiment of the present disclosure. According to one embodiment, the computing device 700 may include at least one processor 702 that executes at least one computer-readable instruction stored or encoded in a computer-readable storage medium (ie, memory 704).

[0133] It should be understood that the computer executable instructions stored in the memory 704, when executed, cause the at least one processor 702 to perform the various operations and functions described above in conjunction with Figures 1-6 in various embodiments of the present disclosure.

[0134] According to one embodiment, a non-transitory machine-readable medium is provided. The non-transitory machine-readable medium may have machine-executable instructions, which, when executed by a machine, enable the machine to perform various operations and functions described above in conjunction with FIG. 1-6 in various embodiments of the present disclosure.

[0135] According to one embodiment, a computer program is provided, including computer-executable instructions, which, when executed, enable at least one processor to perform the various operations and functions described above in conjunction with Figures 1-6 in various embodiments of the present disclosure.

[0136] According to one embodiment, a computer program product is provided, including computer-executable instructions, which, when executed, enable at least one processor to perform the various operations and functions described above in conjunction with Figures 1-6 in various embodiments of the present disclosure.

[0137] It should be understood that the various embodiments in this specification are described in a progressive manner, and reference can be made to the common or similar parts of the various embodiments. Each embodiment focuses on the differences from the other embodiments. For example, the above-mentioned apparatus embodiments, computing device embodiments, and machine-readable storage medium embodiments are generally similar to the method embodiments, so their descriptions are relatively simple. For relevant details, reference can be made to the descriptions of the method embodiments.

[0138] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0139] Not all steps and units in the above processes and system structure diagrams are required, and some steps or units may be omitted according to actual needs. The device structures described in the above embodiments can be physical structures or logical structures, that is, some units may be implemented by the same physical entity, or some units may be implemented by multiple physical entities, or may be implemented by certain components in multiple independent devices.

[0140] The specific embodiments described above in conjunction with the accompanying drawings describe exemplary embodiments, but do not represent all embodiments that can be implemented or fall within the scope of protection of the claims. The term "exemplary" used throughout this specification means "used as an example, instance, or illustration" and does not mean "preferred" or "having advantages" over other embodiments. For the purpose of providing an understanding of the described technology, the specific embodiments include specific details. However, these technologies can be implemented without these specific details. In some instances, in order to avoid obscuring the concepts of the described embodiments, well-known structures and devices are shown in block diagram form.

[0141] The foregoing description of the present disclosure is provided to enable any person skilled in the art to implement or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is intended to be consistent with the widest range of principles and novel features disclosed herein.

[0142] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

[0143] Nouns and pronouns referring to persons in this patent application are not limited to a specific gender.

Claims

1. A NETCONF-based communication method (300), the method being executed on a management device, comprising: The management device establishes a standard NETCONF session with the managed device (S302); The management device creates a group for the managed device (S304); The management device sends group configuration parameters to the managed device through a standard NETCONF session so that the managed device joins the group (S306); The management device sends a multicast request message to the group (S308); as well as The management device receives a response message from the managed device through the standard NETCONF session (S310).

2. The method (300) of claim 1, wherein: The group configuration parameters include at least one of the following: management device IP address, multicast IP address, multicast listening port number, encryption key.

3. The method (300) of claim 1, further comprising: The management device sends a new group configuration message to the managed device through a standard NETCONF session, and after receiving a correct response message, moves the managed device to a new group (S312).

4. The method (300) of claim 1, further comprising: The management device sends a removal request to the managed device through a standard NETCONF session, and after receiving a confirmation message from the managed device, deletes the managed device from the group (S314).

5. The method (300) of claim 1, further comprising: The management device sends a delete group message to the group, and after receiving confirmation messages from all managed devices, deletes the group (S316).

6. A NETCONF-based communication method (400), the method being executed on a managed device, comprising: The managed device and the management device establish a standard NETCONF session (S402); The managed device receives the group configuration parameters from the management device (S404); The managed device joins the corresponding group according to the group configuration parameters, and receives the group information from the management device. broadcast request message and decode it (S406); and The managed device sends a response message to the management device through the standard NETCONF session in response to the decoded multicast request message (S408).

7. A NETCONF-based communication method (200), comprising: The management device and the managed device establish a standard NETCONF session (S202); The management device creates a group for the managed device (S204); The management device sends group configuration parameters to the managed device through a standard NETCONF session (S206); The managed device that receives the group configuration parameters joins the group (S208); When the management device wants to obtain information from a group of managed devices, the management device sends a multicast request message to the group (S210); All managed devices receive the multicast request message from the management device and decode it (S212); as well as The managed device sends a response message to the management device through the standard NETCONF session (S214).

8. A NETCONF-based communication device (500), the communication device being arranged on a management device, comprising: A standard session establishing unit (502), configured to establish a standard NETCONF session with a managed device; A group creation unit (504), configured to create a group for the managed device; A group configuration parameter sending unit (506), configured to send group configuration parameters to the managed device through a standard NETCONF session so that the managed device joins the group; An acceleration unit (508) configured to send a multicast request message to the group; as well as The response message receiving unit (510) is configured to receive a response message from the managed device through the standard NETCONF session.

9. A NETCONF-based communication device (600), the communication device being arranged on a managed device, comprising: A standard session establishing unit (602) is configured to establish a standard NETCONF session between a managed device and a management device; A group configuration parameter receiving unit (604), configured to receive group configuration parameters from a management device; An acceleration unit (606) is configured to enable the managed device to join a corresponding group according to the group configuration parameters, receive a multicast request message from the management device, and decode the multicast message; The response message sending unit (608) is configured to reply a response message to the management device through the standard NETCONF session in response to the decoded multicast request message.

10. A computing device (700), comprising: at least one processor (702); as well as A memory (704) coupled to the at least one processor (702), the memory being used to store instructions, and when the instructions are executed by the at least one processor (702), the processor (702) executes the method according to any one of claims 1-5, 6, and 7.

11. A non-transitory machine-readable storage medium storing executable instructions, which, when executed, cause the machine to perform the method according to any one of claims 1-5, 6, and 7.

12. A computer program product tangibly stored on a computer readable medium and comprising computer executable instructions which, when executed, cause at least one processor to perform the method according to any one of claims 1-5, 6, 7.

Images