Communication method and apparatus

Abstract

The method and device can greatly reduce the complexity of interconnection and cooperation between management nodes and improve the efficiency of interconnection and cooperation. The method comprises: receiving first information from a first managed node, the first information being used to indicate that the first managed node agrees to join a first management group or to request the first managed node to join the first management group; receiving second information from a second managed node, the second information being used to indicate that the second managed node agrees to join the first management group or to request the second managed node to join the first management group; and determining the first management group based on the first information and the second information, the first management group comprising information associated with the first managed node and information associated with the second managed node, and the first management group being used for interconnection and cooperation between a system corresponding to the first managed node and a system corresponding to the second managed node.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to communication methods and apparatus. Background Technology

[0002] There are multiple systems within the region, and each system has a management node. When a system needs to interconnect and collaborate with other systems within the region, the management node in that system needs to establish an interconnection relationship with the management nodes in other systems.

[0003] Currently, when interconnecting multiple management nodes within a region, maintenance personnel typically need to manually configure these nodes. However, when the number of management nodes to be interconnected is large, the high complexity of configuring the nodes and the high skill requirements of personnel make achieving inter-system interconnection and collaboration difficult and inefficient. Summary of the Invention

[0004] This application provides a communication method and apparatus that can greatly reduce the complexity of interconnection and collaboration between management nodes and improve the efficiency of interconnection and collaboration.

[0005] Firstly, a communication method is provided. This method can be executed by a master management node, by a module (e.g., processor, chip, or chip system) applied to the master management node, or by a logical node, logical module, or software capable of implementing all or part of the functions of the master management node. The method includes: receiving first information from a first managed node, the first information indicating that the first managed node agrees to join a first management group, or requesting the first managed node to join the first management group; receiving second information from a second managed node, the second information indicating that the second managed node agrees to join the first management group, or requesting the second managed node to join the first management group; and determining a first management group based on the first and second information, the first management group including information associated with the first managed node and information associated with the second managed node, the first management group being used for interconnection and collaboration between the system corresponding to the first managed node and the system corresponding to the second managed node. For example, the first managed node is relative to the master management node, and the first managed node can actually be (or can be understood as) a management node in the system corresponding to the first managed node.

[0006] In the above technical solution, information associated with multiple managed nodes can be added to a first management group. This allows managed nodes to obtain information associated with other managed nodes in other systems when they need to interconnect and collaborate. Based on this information, they can then interconnect with the managed node system without manually configuring the interconnection relationships between the associated nodes. This solves the current problems of high difficulty and low efficiency in achieving interconnection and collaboration between systems, reduces configuration complexity, saves manpower costs, and significantly reduces the complexity and efficiency of interconnection and collaboration between systems.

[0007] In conjunction with the first aspect above, in one possible implementation, where the first information is used to indicate that the first managed node agrees to join the first management group, the first information is a first response information, and the method further includes: sending a first request information to the first managed node, the first request information being used to request the first managed node to join the first management group.

[0008] In the above technical solution, the master management node can send a first request message to the first managed node to actively request the first managed node to join the first management group. Correspondingly, the first managed node can respond to the request from the master management node and passively join the first management group.

[0009] In conjunction with the first aspect above, in one possible implementation, the first request information includes first authentication information and first system information associated with the first managed node; the information associated with the first managed node includes the first authentication information and first system information associated with the first managed node, or includes second authentication information and second system information associated with the first managed node; the first authentication information and the second authentication information are authentication information for different systems; the first system information and the second system information are system interface information opened for different systems.

[0010] In the above technical solution, the authentication information and system information associated with the first managed node included in the first request information sent by the master management node can be the same as or different from the authentication information and system information in the information associated with the first managed node. In this way, the first managed node can expose the same or different authentication information and system information to the master management node and other managed nodes, enabling the master management node and other managed nodes to communicate with the first managed node using the same or different authentication information and system information.

[0011] In conjunction with the first aspect above, in one possible implementation, the first request information further includes at least one of the following: the identifier of the first management group, the system information of the first system, and the authentication information of the first system; and / or, the first response information includes at least one of the following: the system information of the first system and the authentication information of the first system; wherein, the first system is the system where the main management node is located.

[0012] In the above technical solution, the identifier of the first management group included in the first request information can enable the first managed node to clearly identify the identifier of the management group it wants to join; the system information and authentication information of the first system can enable the first managed node to return the target when returning response information.

[0013] In conjunction with the first aspect above, in one possible implementation, where the first information is used to request the first managed node to join the first management group, the first information is a second request information, and the method further includes: sending a second response information to the first managed node, the second response information being used to indicate agreement to the first managed node joining the first management group.

[0014] In the above technical solution, the first managed node can send a second request message (first message) to the master management node to actively request to join the first management group. Correspondingly, the master management node can respond to the request of the first managed node, enabling the first managed node to join the first management group.

[0015] In conjunction with the first aspect above, in one possible implementation, the second request information includes first authentication information and first system information associated with the first managed node, and the information associated with the first managed node includes the first authentication information and first system information associated with the first managed node; or, the second request information includes first authentication information, first system information, second authentication information, and second system information associated with the first managed node, and the information associated with the first managed node includes the second authentication information and second system information associated with the first managed node; the first authentication information and the second authentication information are authentication information for different systems; the first system information and the second system information are system interface information opened for different systems.

[0016] In the above technical solution, when the second request information includes the first authentication information and the first system information associated with the first managed node, and the information associated with the first managed node includes the first authentication information and the first system information associated with the first managed node, it is stated that the authentication information and system information associated with the first managed node included in the second request information are the same as the authentication information and system information in the information associated with the first managed node. When the second request information includes the first authentication information, the first system information, the second authentication information, and the second system information associated with the first managed node, and the information associated with the first managed node includes the second authentication information and the second system information associated with the first managed node, it is stated that the authentication information and system information associated with the first managed node included in the second request information are different from the authentication information and system information in the information associated with the first managed node.

[0017] In other words, the authentication information and system information associated with the first managed node included in the second request information sent by the first managed node can be the same as or different from the authentication information and system information in the information associated with the first managed node. In this way, the first managed node can expose the same or different authentication information and system information to the master management node and other managed nodes, enabling the master management node and other managed nodes to communicate with the first managed node using the same or different authentication information and system information.

[0018] In conjunction with the first aspect above, in one possible implementation, the second request information further includes at least one of the following: the identifier of the first management group, the system information of the first system, and the authentication information of the first system; and / or, the second response information includes at least one of the following: the first authentication information associated with the first managed node and the first system information.

[0019] In the above technical solution, the identifier of the first management group included in the second request information can enable the main management node to clearly identify the identifier of the management group that the first managed node wants to join; the system information and authentication information of the first system can enable the first managed node to clearly identify the target of sending the second request information.

[0020] In conjunction with the first aspect described above, in one possible implementation, the method further includes: receiving third request information from a first managed node; the third request information is used to request interconnection and collaboration with a second managed node; and sending third response information, the third response information including information associated with the second managed node.

[0021] In the above technical solution, the first managed node can send a third request message to the master management node to request information associated with the second managed node that needs to be interconnected and coordinated. Correspondingly, the master management node can receive the third request message and send feedback to the first managed node regarding the information associated with the second managed node that needs to be interconnected and coordinated.

[0022] In conjunction with the first aspect described above, in one possible implementation, the method further includes: receiving a fourth request message from a first managed node; the fourth request message being used to request an update of information associated with a second managed node; and sending a fourth response message, the fourth response message including the updated information associated with the second managed node.

[0023] In the above technical solution, the master management node responds to the fourth request information of the first managed node and sends the updated information associated with the second managed node to the first managed node.

[0024] In conjunction with the first aspect described above, in one possible implementation, the method further includes: sending a first management group to the first managed node and / or the second managed node.

[0025] In the above technical solution, the master management node can send a first management group to the first managed node and / or the second managed node, enabling the first managed node and / or the second managed node to achieve interconnection and collaboration based on the first management group. Thus, when the first managed node needs to interconnect and collaborate with other managed nodes, even if the communication link between the first managed node and the master management node fails, it can still achieve interconnection and collaboration based on the first management group, greatly improving the reliability of interconnection and collaboration.

[0026] In conjunction with the first aspect above, in one possible implementation, the first management group further includes the validity period of the information associated with the first managed node, and / or the validity period of the information associated with the second managed node.

[0027] In the above technical solution, the first management group may also include the validity period of the information associated with each managed node, so that the master management node can update the information associated with the managed nodes in the first management group after the validity period of the information associated with the managed nodes expires.

[0028] In conjunction with the first aspect above, in one possible implementation, the information associated with the first managed node includes at least one of the following: node identifier, system information of the system corresponding to the first managed node, or authentication information of the system corresponding to the first managed node.

[0029] In the above technical solution, the information associated with the first managed node includes the node identifier, the system information of the system corresponding to the first managed node, or the authentication information of the system corresponding to the first managed node. The three can be used to achieve authentication and interconnection with the system corresponding to the first managed node.

[0030] Secondly, a communication method is provided. This method can be executed by a first managed node, by a module applied to the first managed node (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the first managed node. The method includes: receiving a first request message from a master management node, the first request message requesting the first managed node to join a first management group; and sending a first response message instructing the first managed node to agree to join the first management group. The first management group includes information associated with the first managed node and information associated with a second managed node, wherein the first managed node and the second managed node correspond to different systems, and the first management group is used for interconnection and collaboration between the systems corresponding to the first managed node and the systems corresponding to the second managed node.

[0031] The technical effects of the second aspect can be referenced from those of the first aspect, and will not be elaborated further here.

[0032] In conjunction with the second aspect above, in one possible implementation, the first request information includes first authentication information and first system information associated with the first managed node; the information associated with the first managed node includes first authentication information and first system information associated with the first managed node, or second authentication information and second system information associated with the first managed node; the first authentication information and the second authentication information are authentication information for different systems; the first system information and the second system information are system interface information opened for different systems.

[0033] In conjunction with the second aspect above, in one possible implementation, the first request information further includes at least one of the following: the identifier of the first management group, the system information of the first system, and the authentication information of the first system; and / or, the first response information includes at least one of the following: the system information of the first system and the authentication information of the first system; wherein, the first system is the system where the main management node is located.

[0034] The technical effects of any possible implementation of the second aspect can be referred to the technical effects of the corresponding or the same implementation of the first aspect, and will not be repeated here.

[0035] Thirdly, a communication method is provided. This method can be executed by a first managed node, by a module applied to the first managed node (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the first managed node. The method includes: sending a second request message to request the first managed node to join a first management group; receiving a second response message to instruct a master management node to agree to the first managed node joining the first management group; the first management group includes information associated with the first managed node and information associated with a second managed node, wherein the first managed node and the second managed node correspond to different systems, and the first management group is used for interconnection and collaboration between the systems corresponding to the first and second managed nodes. The technical effects of this third aspect are analogous to those of the first aspect and will not be elaborated further here.

[0036] In conjunction with the third aspect above, in one possible implementation, the second request information includes first authentication information and first system information associated with the first managed node, and the information associated with the first managed node includes the first authentication information and first system information associated with the first managed node; or, the second request information includes first authentication information, first system information, second authentication information, and second system information associated with the first managed node, and the information associated with the first managed node includes the second authentication information and second system information associated with the first managed node; the first authentication information and the second authentication information are authentication information for different systems; the first system information and the second system information are system interface information opened for different systems.

[0037] In conjunction with the third aspect above, in one possible implementation, the second request information further includes at least one of the following: the identifier of the first management group, the system information of the first system, and the authentication information of the first system; and / or, the second response information includes at least one of the following: the first authentication information and the first system information associated with the first managed node; wherein, the first system is the system where the main management node is located.

[0038] The technical effects of any possible implementation of the third aspect can be referred to the technical effects of the corresponding or the same implementation of the first aspect, and will not be repeated here.

[0039] In conjunction with the second or third aspect described above, in one possible implementation, the method further includes: sending a third request message to the master management node, the third request message being used to request interconnection and collaboration with the second managed node; and receiving a third response message from the master management node, the third response message including information associated with the second managed node.

[0040] In conjunction with the second or third aspect above, in one possible implementation, the method further includes: sending a fourth request message to the main management node when the validity period of the information associated with the second managed node expires; the fourth request message is used to request an update of the information associated with the second managed node; receiving a fourth response message from the main management node; the fourth response message includes the updated information associated with the second managed node.

[0041] In conjunction with the second or third aspect described above, in one possible implementation, the method further includes: receiving a first management group from the master management node.

[0042] In conjunction with the second or third aspect described above, in one possible implementation, the method further includes: determining a second managed node to be interconnected and coordinated with in the first management group; and determining information associated with the second managed node from the first management group.

[0043] In conjunction with the second or third aspect above, in one possible implementation, the method further includes: requesting a fifth request for information from the second managed node, the fifth request for information used to request the second managed node to interconnect and collaborate with the first managed node, the fifth request for information associated with the second managed node, the information associated with the second managed node including system information and authentication information of the system corresponding to the second managed node; and receiving the interconnection and collaboration result from the second managed node.

[0044] In conjunction with the second or third aspect above, in one possible implementation, the information associated with the first managed node includes at least one of the following: node identifier, system information of the system corresponding to the first managed node, and authentication information of the system corresponding to the first managed node.

[0045] The technical effects of any possible implementation of the second or third aspect described above can be referred to the technical effects of the corresponding or the same implementation in the first aspect, and will not be repeated here.

[0046] Fourthly, a communication device is provided for implementing various methods. The communication device includes modules, units, or means corresponding to the implementation of the methods. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

[0047] In some possible designs, the communication device may include a processing module and a transceiver module. The processing module can be used to implement the processing functions in any of the above aspects and any possible implementations thereof. The transceiver module may include a receiving module and a transmitting module, respectively used to implement the receiving function and the transmitting function in any of the above aspects and any possible implementations thereof.

[0048] In some possible designs, the transceiver module can consist of transceiver circuits, transceivers, transceivers, or communication interfaces.

[0049] Fifthly, a communication device is provided, comprising: a processor and a memory; the memory being used to store computer instructions, which, when executed by the processor, cause the communication device to perform the method described in either aspect.

[0050] A sixth aspect provides a communication device, comprising: a processor and a communication interface; the communication interface being used to communicate with a module outside the communication device; the processor being used to execute a computer program or instructions to cause the communication device to perform the method described in any one aspect.

[0051] A seventh aspect provides a communication device comprising: at least one processor; said processor being configured to execute a computer program or instructions stored in a memory to cause the communication device to perform the method described in any aspect. The memory may be coupled to the processor, or may be independent of the processor.

[0052] Eighthly, a communication device (e.g., the communication device may be a chip or a chip system) is provided, the communication device including a processor for implementing the functions involved in any one of the first to third aspects.

[0053] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0054] In some possible designs, when the device is a chip system, it can be composed of chips or contain chips and other discrete components.

[0055] It is understood that the communication device provided in the fourth to eighth aspects may be the main management node in the first aspect, or a module or unit (e.g., a chip, chip system, or circuit) in the main management node that executes the methods / operations / steps / actions described in the first aspect, or a module or unit that can be used in conjunction with the main management node, or a logic node, logic module, or software that can implement all or part of the functions of the main management node; or, the communication device may be the first managed node in the second aspect, or a module or unit (e.g., a chip, chip system, or circuit) in the first managed node that executes the methods / operations / steps / actions described in the second aspect, or a module or unit that can be used in conjunction with the first managed node, or a logic node, logic module, or software that can implement all or part of the functions of the first managed node.

[0056] It is understandable that when the communication device provided in any of the fourth to eighth aspects is a chip, the sending action / function of the communication device can be understood as outputting information, and the receiving action / function of the communication device can be understood as inputting information.

[0057] A ninth aspect provides a computer-readable storage medium storing a computer program or instructions that, when executed on a communication device, enable the communication device to perform the method described in any one of the first to third aspects.

[0058] In a tenth aspect, a computer program product containing instructions is provided, which, when run on a communication device, enables the communication device to perform the method described in any one of the first to third aspects.

[0059] Eleventhly, a communication system is provided, comprising a master management node and a first managed node. The master management node is configured to execute the method described in any possible design of the first aspect, and the first managed node is configured to execute the method described in the second or third aspect and any possible design thereof.

[0060] The technical effects of any of the design methods in aspects four through eleven can be found in the technical effects of different design methods in aspects one through three, and will not be repeated here. Attached Figure Description

[0061] Figure 1 A schematic diagram illustrating the management relationship between management nodes provided in this application;

[0062] Figure 2 A schematic diagram of a fault delimitation and localization scenario provided in this application;

[0063] Figure 3 A schematic diagram of an enterprise networking scenario provided for this application;

[0064] Figure 4 A diagram illustrating a management relationship provided for this application;

[0065] Figure 5 A schematic diagram of the architecture of a communication system provided in this application;

[0066] Figure 6 A schematic diagram of another communication system architecture provided in this application;

[0067] Figure 7 A schematic diagram of interconnection and collaboration provided for this application;

[0068] Figures 8-14 A flowchart illustrating the communication method provided in this application;

[0069] Figures 15-16 A schematic diagram of the communication device provided in this application. Detailed Implementation

[0070] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0071] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0072] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0073] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0074] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0075] It is understood that in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require a judgment action to be performed during implementation, nor do they imply any other limitations.

[0076] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0077] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of this application.

[0078] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.

[0079] I. Management Nodes.

[0080] A management node can also be called a management device, manager, or master. A management node is a software or hardware node used to manage specific devices. Through a management node, management operations can be performed on specific devices within a system. For example, a network management node (hereinafter referred to as a management node) can manage several network devices in a network system, an IoT management node can manage several IoT devices in an IoT system, an industrial management node can manage several industrial devices in an industrial system, and a medical management node can manage several medical devices in a medical system. The software of a management node can be deployed on a cloud server. When the services provided by a management node are integrated and offered to other interacting parties, it is also called a management system.

[0081] II. Equipment.

[0082] Equipment refers to software or hardware devices used to provide a certain function. For example, network equipment provides the functions required for network communication, while industrial equipment provides the functions required for industrial production.

[0083] Devices are typically managed by their corresponding management nodes (i.e., the management nodes within the system to which they belong). For example, network devices are managed by network management nodes, and industrial devices are managed by industrial management nodes.

[0084] III. Interaction between management nodes.

[0085] When multiple management nodes interact, an interconnection relationship must be established between the nodes that need to interact before interaction can occur. Within this management relationship, there are two roles: management nodes and managed nodes. For example, in a management relationship where management nodes A, B, and C interact, management node A can be the management node, while management nodes B and C can be the managed nodes.

[0086] The management node can request information from the managed nodes, meaning it can respond to requests from the managed nodes by sending the requested information back to them. Furthermore, the management node can also perform management operations and request adjustments to management configurations from the managed nodes.

[0087] A managed node can also be called a managed node or a worker node. A managed node can respond to requests and push information to the management node. A managed node can be managed by one or more management nodes. In scenarios where a managed node is managed by multiple management nodes, a management device table is maintained on the managed node to record information about the different management nodes. This table records information such as the identification information, interface / service permissions, and push conditions of the multiple management nodes corresponding to the managed node.

[0088] The above provides an explanation of the relevant terms used in this application.

[0089] The following describes the application scenarios of this application.

[0090] Currently, enterprises or industrial parks often have a wide variety of network devices from numerous manufacturers. To manage these devices, management nodes are used to manage network devices with similar attributes. A management node and the devices it manages are considered a system. Thus, an industrial park may contain multiple systems, such as a security system (including management node A, cameras, access control equipment, etc.) and an office system (including management node B, projectors, computers, printers, etc.). However, these systems coexist in isolation, leading to low management efficiency. Furthermore, to manage multiple management nodes, higher-level management nodes can be set up within the industrial park to manage multiple lower-level management nodes.

[0091] Multiple systems exist within the region, each with a management node. Taking a fault localization scenario as an example, when a terminal service malfunctions, multiple systems need to interact to locate the fault. When a system needs to interconnect and collaborate with other systems within the region, the management node in that system needs to establish interconnection relationships with the management nodes in other systems.

[0092] For example, such as Figure 1 As shown, management node A manages management nodes B and C (where, from a management relationship perspective, management node A is a management node, and management nodes B and C are managed nodes). Management node A is responsible for the management and maintenance of the entire system's end-to-end services. When an end-to-end service malfunctions (e.g., website access failure), management node A coordinates management nodes B and / or C for cross-domain troubleshooting. However, when a device managed by management node B malfunctions (e.g., the upload speed of a storage device managed by management node B is less than a preset threshold), cross-domain troubleshooting of the storage device managed by management node B is not within the management scope of management node A. Instead, management node C needs to coordinate and collaborate to complete the cross-domain troubleshooting and repair.

[0093] In specific fault delimitation and localization scenarios, such as Figure 2As shown, this scenario includes a main management node, management node 1, management node 2, management node 3, and management node 4. In this scenario, the main management node acts as the manager, overseeing the managed nodes 1, 2, 3, and 4. Management node 1 manages the host and storage devices; management node 2 manages devices such as access 1, access 2, aggregation 1, aggregation 2, aggregation 3, aggregation 4, routing 1, and routing 2; management node 3 manages devices such as aggregation switches, access gateways, and access switches; and management node 4 manages various camera devices (e.g., intelligent PTZ cameras, face capture cameras, dome cameras, and vehicle recognition devices). Figure 2 The diagram shows two links. One link includes: host, access 1, aggregation 2, access 2, storage device; the other link includes: host, access 1, aggregation 1, aggregation 4, router 2, aggregation switch, access gateway, access switch.

[0094] In this scenario, in one case, when a terminal service fails (e.g., a website becomes inaccessible or the camera device managed by management node 4 goes offline), the main management node initiates end-to-end network fault diagnosis, location, and repair. In another case, when a storage device managed by management node 1 experiences slow upload speeds, management node 1 collects the host data plane Internet Protocol (IP) address, storage device IP address, and client IP address of the target service. Then, management node 1 corresponding to the storage device collaborates with the management nodes corresponding to other devices in the same link as the storage device (e.g., management node 2 corresponding to access 1 and / or management node 3 corresponding to the aggregation switch in the same link as the storage device) to diagnose, locate, and repair the fault.

[0095] To achieve the aforementioned troubleshooting, location, and repair, interconnection and collaboration among management nodes in multiple systems are required. However, the prerequisite for achieving interconnection and collaboration among multiple management nodes is the implementation of interconnection configurations between each management node.

[0096] Currently, when interconnecting multiple management nodes within a region, maintenance personnel typically need to manually configure these nodes. Configuration usually consists of two parts: 1. Authentication configuration, which involves configuring machine interface information, including address (internet protocol, IP), port, username, and password; 2. Relationship configuration, which involves configuring inter-system capability sets (interface sets) and interface call permission information.

[0097] Specifically, with Figure 3The example shown is an enterprise network. This network topology includes a factory core switching network, an office network, a security monitoring network, a production network, and a management node center. The switches in the factory core switching network can connect to the office network, security monitoring network, production network, management node center, and other network communication systems, enabling the main management node to manage each network. The office network manages the cloud platform and various office equipment (e.g., computers, printers) through the first management node; the security monitoring network manages the cloud platform and various security equipment (e.g., cameras, turnstiles) through the second management node; and the production network manages various production equipment through the third and fourth management nodes in the server area and the cloud platform in the machine area. The management node center provides comprehensive management of all management nodes within the enterprise network.

[0098] From the perspective of management relationships, Figure 3 The enterprise network shown includes various management relationships. These relationships can be one-way or two-way. For example, Figure 4 As shown, a one-way management relationship can be: a master node (as the manager) manages multiple managed nodes, including a first management node, a cloud platform, a second management node, a third management node, a fourth management node, and other management nodes. A two-way management relationship can be: a cloud platform (as the manager) manages a second management node (as a managed node); or a second management node (as the manager) manages a cloud platform (as a managed node). A two-way management relationship can also be: a first management node (as the manager) manages a cloud platform (as a managed node); or a cloud platform (as the manager) manages a first management node (as a managed node). A two-way management relationship can also be: a third management node (as the manager) manages a fourth management node (as a managed node); or a fourth management node (as the manager) manages a third management node (as a managed node). Finally, a two-way management relationship can be: a cloud platform (as the manager) manages a third management node (as a managed node); or a third management node (as the manager) manages a cloud platform (as a managed node).

[0099] Therefore, enterprise networking is a one-to-many master-slave relationship management, that is, the relationship management between managers and managed nodes. To achieve interconnection configuration among all managed nodes, according to the traditional configuration method, it is necessary to complete N*(N-1)*2 master-slave configurations, where N is the number of managed nodes. When the number of management nodes requiring interconnection and collaboration is too large, the high complexity of configuration between management nodes and the high skill requirements of personnel make it difficult and inefficient to achieve interconnection and collaboration between systems.

[0100] In view of this, this application proposes a communication method in which a master management node receives first information from a first managed node, indicating that the first managed node agrees to join a first management group, or requests the first managed node to join the first management group. It also receives second information from a second managed node, indicating that the second managed node agrees to join the first management group, or requests the second managed node to join the first management group. That is, the first and second information can instruct the corresponding managed nodes to join the first management group. Therefore, the master management node can add the first and second managed nodes to the first management group based on the first and second information, thus defining a first management group that includes information associated with the first and second managed nodes. Furthermore, the first management group can also be used for interconnection and collaboration between the systems corresponding to the first and second managed nodes. Thus, this technical solution can add information associated with multiple managed nodes to the first management group. This allows managed nodes to obtain information associated with other managed nodes in other systems when they need to interconnect and collaborate. Based on this information, they can then interconnect with the managed node system without manually configuring the interconnection relationships between the associated nodes. This solves the current problems of high difficulty and low efficiency in achieving interconnection and collaboration between systems, reduces configuration complexity, saves manpower costs, and significantly reduces the complexity and efficiency of interconnection and collaboration between systems.

[0101] The technical solutions of this application embodiment can be used in various communication systems, including third-generation partnership project (3GPP) communication systems, such as fourth-generation (4G) systems like Long Term Evolution (LTE), 5G systems like New Radio (NR), LTE and 5G hybrid networking systems, non-terrestrial networks (NTN), or other next-generation communication systems. The communication system can also be a non-3GPP communication system; there is no limitation on this.

[0102] The communication systems described above are merely illustrative examples, and are not limited to those described herein. The communication systems provided in this application do not impose any limitations on the solutions described herein. This will be explained uniformly here and will not be repeated below.

[0103] Figure 5 This diagram illustrates the architecture of a possible, non-limiting communication system. (For example...) Figure 5As shown, the communication system includes multiple systems 500, each system 500 including a management node 510 and multiple devices 520. The multiple devices 520 in system 500 are managed by the management node 510.

[0104] Optional, such as Figure 6 As shown, the management nodes 510 in multiple systems 500 are connected through communication links.

[0105] Optionally, the management node 501 can be either a primary management node or a managed node. For example, the first system 500 includes a primary management node and multiple devices 520, the second system 500 includes a first managed node and multiple devices 520, and the third system 500 includes a second managed node and multiple devices 520.

[0106] Of course, the above only illustrates the existence of multiple managed nodes in a communication system using the first and second managed nodes. In reality, a communication system can include even more managed nodes, such as a third, fourth, and Nth managed node, where N is a positive integer. Specifically, the third managed node corresponds to the fourth system 500, the fourth managed node corresponds to the fifth system 500, and the Nth managed node corresponds to the (N+1)th system 500.

[0107] Optionally, when management node 510 acts as the primary management node, management node 510 has at least one of the following functions:

[0108] 1. The function of creating the first management group on the main management node.

[0109] 2. Function to write the identifier (ID) of the first management group.

[0110] 3. The function of writing and / or modifying information associated with managed nodes in the first management group. For example, taking the function of writing information associated with managed nodes in the first management group as an example, the management node 510 can write information associated with managed nodes during the process of adding each managed node to the first management group. The associated information includes, but is not limited to, at least one of the following: node identifier, system information of the system corresponding to the managed node, or authentication information of the system corresponding to the managed node.

[0111] 4. Function to receive information associated with the managed node.

[0112] 5. The function of synchronizing the updated information of the first management group to each managed node after the information in the first management group is updated.

[0113] 6. The first management group is used for flexible networking among managed nodes. For example, it receives requests from managed nodes for interconnection and collaboration, and sends interconnection and collaboration-related information about the managed nodes to the node that sent the request.

[0114] 7. Add an expiration date to the information associated with the managed node. For example, after the expiration date, the first managed node needs to request the information associated with the second managed node from the management node again.

[0115] Optionally, when the management node 510 acts as a managed node, the management node 510 has at least one of the following functions:

[0116] 1. The function of sending information associated with the managed node to the master management node.

[0117] 2. Send a request message to the main management node to request the managed nodes in the first management group to quickly form a network and perform interconnection and collaboration.

[0118] 3. Function to receive (or return) information related to interconnection and collaboration between managed nodes sent by the master management node.

[0119] 4. Receive the first management group sent by the master management node, and based on the first management group, realize rapid networking with other managed nodes to achieve interconnection and collaboration.

[0120] 5. Save the updated first management group, and based on the first management group, realize rapid networking with other managed nodes to achieve interconnection and collaboration.

[0121] 6. Receive information from the master management node regarding the associated information of the managed node with an expiration date, and request the master management node to update the associated information of the managed node again after the expiration date.

[0122] For example, the communication system provided in this embodiment includes five systems 500, and the first system 500 includes a master management node, the second system 500 includes a first managed node, the third system 500 includes a second managed node, the fourth system 500 includes a third managed node, and the fifth system 500 includes a fourth managed node. Figure 7As shown, when a first managed node needs to interconnect and collaborate with other managed nodes, it can send a request message to the master management node. The master management node processes the request message and returns to the first managed node the information associated with the interconnected and collaborative managed nodes in the first management group. For example, when a first managed node needs to interconnect and collaborate with a second managed node, it can send a request message to the master management node. The master management node processes the request message and returns to the first managed node the information associated with the second managed node from among the M managed node association information in the first management group. This information associated with the second managed node includes the node identifier of the second managed node, the system information of the system corresponding to the second managed node, or the authentication information of the system corresponding to the second managed node.

[0123] It should be noted that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0124] The following is combined Figure 5 The communication system shown here, taking the interaction between multiple management nodes as an example, describes the communication method provided in the embodiments of this application. It should be noted that in the following embodiments of this application, the message names, parameter names, or information names between multiple management nodes are just examples, and other names may be used in other embodiments. The method provided in this application does not specifically limit these names.

[0125] It is understood that in the embodiments of this application, the management node may execute some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also execute other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments of this application, and it is not necessarily necessary to execute all the operations in the embodiments of this application.

[0126] It is understood that this application uses multiple management nodes as the execution entities for illustrating the interaction, but this application does not limit the execution entities for the interaction. For example, the method executed by the main management node in this application can also be executed by a module (e.g., a chip, chip system, or processor) applied to the main management node, or by a logical node, logical module, or software capable of implementing all or part of the main management node's functions. For example, the method executed by the first managed node in this application can also be executed by a module (e.g., a chip, chip system, or processor) applied to the first managed node, or by a logical node, logical module, or software capable of implementing all or part of the first managed node's functions.

[0127] Furthermore, in this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For example, "the master management node sending information" can be understood as the master management node sending information to another device (such as the first managed node), or it can be understood as logical module 1 (such as the processing module) in the master management node sending information to logical module 2 (such as the transceiver module) in the first managed node.

[0128] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "the main management node receiving information" can be understood as the main management node receiving information from another device (such as the first managed node), or it can be understood as logical module 1 (such as the processing module) in the main management node receiving information from logical module 2 (such as the transceiver module) in the first managed node.

[0129] In this application, phrases such as "sending information to... (e.g., the first managed node)" or related illustrations in the accompanying drawings can be understood as the destination of the information being the first managed node. This can include sending information directly or indirectly to the first managed node. Similarly, phrases such as "receiving information from... (e.g., the master management node)," "receiving information from... (e.g., the master management node)," or "receiving information sent by (e.g., the master management node)," or related illustrations in the accompanying drawings, can be understood as the source of the information being the management node. This can include receiving information directly or indirectly from the management node. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be elaborated further here.

[0130] See Figure 8 The following is a flowchart of a communication method provided in an embodiment of this application, which may include the following steps S801-S803.

[0131] S801, the first managed node sends the first information to the master management node. Correspondingly, the master management node receives the first information from the first managed node.

[0132] The first information is used to instruct the first managed node to agree to join the first management group, or to request the first managed node to join the first management group.

[0133] In some embodiments, when the first information is used to indicate that the first managed node agrees to join the first management group, the specific implementation scheme of S801 is as shown in Embodiment 1 below, and will not be repeated here.

[0134] In other embodiments, when the first information is used to request the first managed node to join the first management group, the specific implementation scheme of S801 is as shown in Embodiment 2 below, and will not be repeated here.

[0135] As one possible implementation, the first managed node may be the management node 510 in one of the systems 500 of the aforementioned communication system 50. The master management node may be the management node 510 in the first system 500 of the aforementioned communication system 500, which can be used to manage other systems 500.

[0136] S802, the second managed node sends the second information to the master management node, and correspondingly, the master management node receives the second information from the second managed node.

[0137] The second information is used to instruct the second managed node to agree to join the first management group, or to request the second managed node to join the first management group.

[0138] In some embodiments, when the second information is used to indicate that the second managed node agrees to join the first management group, and when the second information is used to request the second managed node to join the first management group, the process of sending and receiving the second information between the second managed node and the master management node refers to the embodiment shown in S801, and will not be repeated here.

[0139] It should be noted that this application does not limit the execution order of S801 and S802. That is, S801 can be executed before S802, S801 can be executed after S802, and S801 and S802 can be executed simultaneously.

[0140] Of course, in addition to receiving the first information from the first managed node and the second information from the second managed node, if the communication system also includes a third managed node, a fourth managed node, and so on, as well as an Nth managed node, the third managed node can send a third information to the master management node, the fourth managed node can send a fourth information to the master management node, and the Nth managed node can send an Nth information. Correspondingly, the master management node can also receive the third information from the third managed node, the fourth information from the fourth managed node, and so on, as well as the Nth information from the Nth managed node.

[0141] The third message is used to instruct the third managed node to agree to join the first management group, or to request the third managed node to join the first management group; the fourth message is used to instruct the fourth managed node to agree to join the first management group, or to request the fourth managed node to join the first management group. The Nth message is used to instruct the Nth managed node to agree to join the first management group, or to request the Nth managed node to join the first management group.

[0142] S803. The main management node determines the first management group based on the first information and the second information.

[0143] The first management group includes information associated with the first managed node and information associated with the second managed node. The first management group is used for interconnection and collaboration between the system corresponding to the first managed node and the system corresponding to the second managed node.

[0144] Optionally, the information associated with the first managed node includes at least one of the following: node identifier, system information of the system corresponding to the first managed node, or authentication information of the system corresponding to the first managed node.

[0145] Optionally, the information associated with the second managed node includes at least one of the following: node identifier, system information of the system corresponding to the second managed node, or authentication information of the system corresponding to the second managed node.

[0146] Optionally, the first management group also includes information associated with the third managed node, the fourth managed node, and so on, as well as information associated with the Nth managed node. In this case, the first management group is used for interconnection and collaboration between the systems corresponding to the N managed nodes.

[0147] In one possible implementation, the master management node can create a first management group and write its identifier. At this point, the first management group does not contain information associated with managed nodes. After receiving the first message, the master management node writes the information associated with the first managed node into the first management group; and after receiving the second message, the master management node writes the information associated with the second managed node into the first management group. This application does not impose any restrictions on the order in which the master management node writes the information associated with the first managed node and the information associated with the second managed node into the first management group.

[0148] Optionally, in the above possible implementations, the process of the main management node creating the first management group and writing the identifier of the first management group can be implemented before any of steps S801, S802 or S803, or after S801 or S802. This application does not limit this.

[0149] Optionally, in some embodiments, the first management group further includes the validity period of information associated with the first managed node, and / or the validity period of information associated with the second managed node. After the validity period of the information associated with the first managed node expires, the master management node can update the information associated with the first managed node. After the validity period of the information associated with the second managed node expires, the master management node can update the information associated with the second managed node.

[0150] Based on the above technical solution, this application proposes a communication method in which a master management node receives first information from a first managed node, indicating that the first managed node agrees to join a first management group, or requesting that the first managed node join the first management group. It also receives second information from a second managed node, indicating that the second managed node agrees to join the first management group, or requesting that the second managed node join the first management group. In other words, the first and second information can instruct the corresponding managed nodes to join the first management group. Therefore, the master management node can add the first and second managed nodes to the first management group based on the first and second information, thus defining a first management group that includes information associated with the first and second managed nodes. Furthermore, the first management group can also be used for interconnection and collaboration between the systems corresponding to the first and second managed nodes. Thus, this technical solution can add information associated with multiple managed nodes to the first management group. This allows managed nodes to obtain information associated with other managed nodes in other systems when they need to interconnect and collaborate. Based on this information, they can then interconnect with the managed node system without manually configuring the interconnection relationships between the associated nodes. This solves the current problems of high difficulty and low efficiency in achieving interconnection and collaboration between systems, reduces configuration complexity, saves manpower costs, and significantly reduces the complexity and efficiency of interconnection and collaboration between systems.

[0151] Furthermore, the communication method provided in this application can be flexibly configured for networking based on actual business needs, enabling inter-system collaboration. The communication method also provides multiple methods for joining management groups, meeting the needs of administrators to operate on both the main management node and each managed node, thus improving feasibility.

[0152] Hereinafter, through Embodiment 1, a detailed implementation scheme of S801 is provided when the first information is used to instruct the first managed node to agree to join the first management group; through Embodiment 2, a detailed implementation scheme of S801 is provided when the first information is used to request the first managed node to join the first management group.

[0153] Example 1

[0154] As one possible embodiment of this application, such as Figure 9As shown, when the first information is used to instruct the first managed node to agree to join the first management group, the first information is the first response information (that is, the specific implementation of S801 includes: the first managed node sending the first response information to the master management node, and correspondingly, the master management node receiving the first response information from the first managed node). Furthermore, before S801, the master management node also sends the first request information to the first managed node, and correspondingly, the first managed node receives the first request information from the master management node. The first request information is used to request the first managed node to join the first management group.

[0155] In some embodiments, the first request information includes first authentication information and first system information associated with the first managed node. In this scenario, the information associated with the first managed node includes the first authentication information and first system information associated with the first managed node, or it includes second authentication information and second system information associated with the first managed node. The first authentication information and the second authentication information are authentication information for different systems; the first system information and the second system information are system interface information exposed for different systems.

[0156] Optionally, the first request information may further include at least one of the following: the identifier of the first management group, the system information of the first system, and the authentication information of the first system; and / or, the first response information may include at least one of the following: the system information of the first system and the authentication information of the first system. Wherein, the first system is the system where the main management node is located.

[0157] It should be noted that if the first request information includes the first authentication information and the first system information associated with the first managed node, and the information associated with the first managed node includes the first authentication information and the first system information associated with the first managed node, it means that the authentication information and interfaces opened by the first managed node for the first system corresponding to the main management node and the system corresponding to the second managed node are the same.

[0158] Conversely, if the first request information includes the first authentication information and the first system information associated with the first managed node, and the information associated with the first managed node includes the second authentication information and the second system information associated with the first managed node, it indicates that the authentication information and interfaces opened by the first managed node for the first system corresponding to the main management node and the system corresponding to the second managed node are different.

[0159] Understandably, since the first managed node has varying degrees of trust in different nodes, it can grant different authentication permissions and system interfaces to different systems to ensure its security. For example, the first managed node can grant first authentication information and first system information to the first system with a trust level greater than a preset threshold, and grant second authentication information and second system information to the systems corresponding to other managed nodes with a trust level less than the preset threshold.

[0160] The following describes the implementation scheme of the main management node adding the first managed node to the first management group, using Example 1, where the first managed node opens the same authentication information and interfaces for the first system corresponding to the main management node and the system corresponding to the second managed node. Example 2 describes the implementation scheme where the first managed node opens different authentication information and interfaces for the first system corresponding to the main management node and the system corresponding to the second managed node.

[0161] Example 1

[0162] like Figure 10 As shown in S1001-S1005, in the communication method provided by this application, when the first information is used to instruct the first managed node to agree to join the first management group, and the authentication information and interfaces opened by the first managed node for the first system corresponding to the master management node and the system corresponding to the second managed node are the same, the process of the master management node joining the first managed node in the first management group can be implemented by the following S1001-S1005.

[0163] S1001. The main management node creates the first management group and writes the identifier of the first management group.

[0164] S1002, The master management node obtains the information associated with the first managed node (including the first system information of the system corresponding to the first managed node and the first authentication information of the system corresponding to the first managed node).

[0165] Optionally, the master management node may respond to user input operations to obtain information associated with the first managed node (that is, the user can actively input information associated with the first managed node on the master management node, and the master management node can obtain the information associated with the first managed node input by the user); the master management node may also obtain information associated with the first managed node from storage media such as databases. This application does not impose any restrictions on the way the master management node obtains information associated with the first managed node.

[0166] S1003, the master management node sends a first request message to the first managed node. Correspondingly, the first managed node receives the first request message from the master management node.

[0167] The first request information includes the identifier of the first management group, the system information of the first system, the authentication information of the first system, the first authentication information associated with the first managed node, and the first system information.

[0168] It should be noted that the first managed node can identify the first management group among multiple management groups by the identifier of the first management group included in the first request information. The master management node can accurately send the first request information to the first managed node among multiple managed nodes by using the first authentication information and first system information associated with the first managed node included in the first request information. Of course, the first managed node can also verify that the first request information is sent to it by the master management node by using the first authentication information and first system information associated with the first managed node included in the first request information. The first managed node can determine the source of the first request information by using the system information and authentication information of the first system; furthermore, when returning the first response information, the first managed node can accurately locate the master management node in the first system by using the system information and authentication information of the first system.

[0169] S1004. The first managed node returns the first response information to the master management node. Correspondingly, the master management node receives the first response information from the first managed node.

[0170] The first response information includes the system information of the first system and the authentication information of the first system.

[0171] It should be noted that when the first managed node returns the first response information, it can accurately locate the main management node in the first system by using the system information and authentication information of the first system, and thus accurately return the first response information to the main management node.

[0172] S1005. The main management node determines the first management group based on the first response information.

[0173] For example, information associated with the first managed node is written into the first management group. Specifically, the specific implementation process of S1005 above refers to the embodiment shown in S803, and will not be repeated here.

[0174] Example 2

[0175] like Figure 11As shown in S1101-S1105, in the communication method provided by this application, when the first information is used to instruct the first managed node to agree to join the first management group, and the authentication information and interfaces opened by the first managed node for the first system corresponding to the master management node and the system corresponding to the second managed node are different, the process of the master management node joining the first managed node in the first management group can be implemented by the following S1101-S1105.

[0176] S1101. The main management node creates the first management group and writes the identifier of the first management group.

[0177] S1102, The master management node obtains the information associated with the first managed node.

[0178] The information associated with the first managed node includes the first system information of the system corresponding to the first managed node and the first authentication information of the system corresponding to the first managed node.

[0179] S1103. The master management node sends a first request message to the first managed node. Correspondingly, the first managed node receives the first request message from the master management node.

[0180] The first request information includes the identifier of the first management group, the system information of the first system, the authentication information of the first system, the first authentication information associated with the first managed node, and the first system information.

[0181] S1104. The first managed node returns a first response message to the master management node. Correspondingly, the master management node receives the first response message from the first managed node.

[0182] The first response information includes system information of the first system, authentication information of the first system, second authentication information associated with the first managed node, and second system information.

[0183] It should be noted that when returning the first response information, the first managed node can accurately locate the master management node in the first system using the system information and authentication information of the first system, thereby accurately returning the first response information to the master management node. The second authentication information and second system information associated with the first managed node are used to write to the first management group, so that other managed nodes can interconnect and collaborate with the first managed node through the second authentication information and second system information associated with the first managed node.

[0184] S1005. The main management node determines the first management group based on the first response information.

[0185] For example, the master management node writes the information associated with the first managed node (including the node identifier of the first managed node, the second authentication information associated with the first managed node, and the second system information associated with the first managed node) into the first management group based on the second authentication information and the second system information associated with the first managed node in the first response information. Specifically, the specific implementation process of S1005 above refers to the embodiment shown in S803, and will not be repeated here.

[0186] As can be seen from Examples 1 and 2 above, the first managed node can adaptively add authentication information and system information to the first management group according to its own needs to ensure its own security.

[0187] In the above embodiment 1, the master management node can actively request the first managed node to join the first management group, thereby realizing the management of the first managed node, so that when the first managed node needs to interconnect and coordinate in the future, the master management node can provide the information associated with the first managed node.

[0188] Example 2

[0189] As one possible embodiment of this application, such as Figure 9 As shown, when the first information is used to request the first managed node to join the first management group, the first information is a second request information (that is, the specific implementation of S801 includes: the first managed node sending the second request information to the master management node, and correspondingly, the master management node receiving the second request information from the first managed node); and, after S801, the master management node also sends a second response information to the first managed node, and correspondingly, the first managed node receives the second response information from the master management node. The second response information is used to indicate agreement to allow the first managed node to join the first management group.

[0190] In some embodiments, the second request information includes first authentication information and first system information associated with the first managed node, and the information associated with the first managed node includes the first authentication information and first system information associated with the first managed node.

[0191] It should be noted that if the second request information includes the first authentication information and the first system information associated with the first managed node, and the information associated with the first managed node includes the first authentication information and the first system information associated with the first managed node, it means that the authentication information and interfaces opened by the first managed node for the first system corresponding to the main management node and the system corresponding to the second managed node are the same.

[0192] In other embodiments, the second request information includes first authentication information, first system information, second authentication information and second system information associated with the first managed node, and the information associated with the first managed node includes the second authentication information and second system information associated with the first managed node.

[0193] It should be noted that when the second request information includes the first authentication information, the first system information, the second authentication information, and the second system information associated with the first managed node, and the information associated with the first managed node includes the second authentication information and the second system information associated with the first managed node, it indicates that the authentication information and interfaces opened by the first managed node for the first system corresponding to the main management node and the system corresponding to the second managed node are different.

[0194] Optionally, the second request information may further include at least one of the following: the identifier of the first management group, the system information of the first system, and the authentication information of the first system; and / or, the second response information may include at least one of the following: the first authentication information and the first system information associated with the first managed node.

[0195] The following describes the implementation scheme of the main management node adding the first managed node to the first management group, using Example 3, where the first managed node has the same authentication information and interfaces for the first system corresponding to the main management node and the system corresponding to the second managed node. Example 4 describes the implementation scheme where the first managed node has different authentication information and interfaces for the first system corresponding to the main management node and the system corresponding to the second managed node.

[0196] Example 3

[0197] like Figure 10 As shown in S1006-S1009, in the communication method provided by this application, when the first information is used to request the first managed node to join the first management group, and the authentication information and interfaces opened by the first managed node for the first system corresponding to the master management node and the system corresponding to the second managed node are the same, the process of the master management node joining the first managed node in the first management group can be implemented by the following S1001 and S1006-S1009.

[0198] S1001. The main management node creates the first management group and writes the identifier of the first management group.

[0199] S1006. The first managed node obtains the system information and authentication information of the first system corresponding to the master management node.

[0200] Optionally, the first managed node may obtain the system information and authentication information of the first system in response to user input operations; the first managed node may also obtain the system information and authentication information of the first system from storage devices such as databases. This application does not impose any restrictions on the method by which the first managed node obtains the system information and authentication information of the first system.

[0201] S1007. The first managed node sends a second request message to the master management node. Correspondingly, the master management node receives the second request message from the first managed node.

[0202] The second request information includes the identifier of the first management group, the system information of the first system, the authentication information of the first system, the first authentication information associated with the first managed node, and the first system information.

[0203] Understandably, the first managed node can determine the address of the master management node based on the system information and authentication information of the first system, and then accurately send the second request information to the master management node. The first authentication information and first system information associated with the first managed node are also used by the first system corresponding to the master management node to verify the received second request information.

[0204] S1008. The main management node processes the second request information and determines the first management group.

[0205] For example, based on the second request information, the node identifier of the first managed node, the first authentication information associated with the first managed node, and the first system information are written into the first management group.

[0206] S1009, the master management node sends a second response message to the first managed node. Correspondingly, the first managed node receives the second response message from the master management node.

[0207] Optionally, the second response information includes the first authentication information and the first system information associated with the first managed node.

[0208] It is understandable that the master management node can accurately determine the first managed node from multiple managed nodes based on the first authentication information and the first system information associated with the first managed node, and then accurately send the second response information to the first managed node.

[0209] Example 4

[0210] like Figure 11As shown in S1106-S1109, in the communication method provided by this application, when the first information is used to request the first managed node to join the first management group, and the authentication information and interfaces opened by the first managed node for the first system corresponding to the master management node and the system corresponding to the second managed node are different, the process of the master management node joining the first managed node in the first management group can be implemented by the following S1101 and S1106-S1109.

[0211] S1101. The main management node creates the first management group and writes the identifier of the first management group.

[0212] S1106. The first managed node obtains the system information and authentication information of the first system corresponding to the master management node.

[0213] Optionally, the process of the first managed node obtaining the system information and authentication information of the first system can be referred to the embodiment shown in S1006, and will not be repeated here.

[0214] S1107. The first managed node sends a second request message to the master management node. Correspondingly, the master management node receives the second request message from the first managed node.

[0215] The second request information includes the identifier of the first management group, the system information of the first system, the authentication information of the first system, the first authentication information associated with the first managed node, the first system information, the second authentication information, and the second system information.

[0216] Specifically, the master management node can identify the first management group from multiple management groups by using the identifier of the first management group. The first managed node can determine the destination address of the second request message as the master management node using the system information and authentication information of the first system, and thus accurately send the second request message to the master management node. Furthermore, the master management node can verify the second request message using the system information and authentication information of the first system. Based on the second authentication information and second system information associated with the first managed node in the second request message, the master management node can add the first managed node to the first management group. Finally, the master management node can determine the destination address of the second response message as the first managed node using the first authentication information and first system information associated with the first managed node, and thus accurately send the second response message to the first managed node.

[0217] S1108. The main management node processes the second request information and determines the first management group.

[0218] In one possible implementation, the master management node writes the node identifier of the first managed node, the second authentication information associated with the first managed node, and the second system information into the first management group based on the second request information.

[0219] S1109. The master management node sends a second response message to the first managed node. Correspondingly, the first managed node receives the second response message from the master management node.

[0220] Optionally, the second response information includes the first authentication information and the first system information associated with the first managed node.

[0221] It is understandable that the master management node can accurately determine the first managed node from multiple managed nodes based on the first authentication information and the first system information associated with the first managed node, and then accurately send the second response information to the first managed node.

[0222] As can be seen from Examples 3 and 4 above, the first managed node can adaptively add authentication information and system information to the first management group according to its own needs to ensure its own security.

[0223] In the above embodiment 2, the first managed node can actively request to join the first management group. Correspondingly, the master management node can respond to the request of the first managed node and add the first managed node to the first management group, thereby realizing the management of the first managed node. So that when the first managed node needs to interconnect and collaborate in the future, the master management node can provide the associated information of the first managed node.

[0224] The following describes in detail the implementation process of interconnection and collaboration between the first managed node and the second managed node through Examples 3 and 4. Specifically, Example 3 describes the implementation process in which the first managed node determines its interconnection and collaboration with the second managed node through the master management node; Example 4 describes the implementation process in which the first managed node independently determines its interconnection and collaboration with the second managed node.

[0225] Example 3

[0226] As one possible embodiment of this application, such as Figure 12 As shown, the process by which the first managed node determines the interconnection and collaboration with the second managed node through the master management node can be implemented through the following S1201-S1202.

[0227] S1201, the first managed node sends a third request message to the master management node. Correspondingly, the master management node receives the third request message from the first managed node.

[0228] The third request information is used to request interconnection and collaboration with the second managed node. Alternatively, the third request information can also be used to request the primary management node to determine the managed node for interconnection and collaboration.

[0229] In one possible implementation, the implementation process of S1201 includes: when the first managed node has a target service and needs to interconnect and coordinate with other managed nodes, the first managed node sends a third request message to the master management node to request interconnect and coordinate with the second managed node, or to request the master management node to determine the managed nodes that need to be interconnected and coordinated to process the target service.

[0230] In one example, a device in the system corresponding to the first managed node experiences a service failure. In this case, interconnection and collaboration with the systems corresponding to other managed nodes are required to achieve cross-domain troubleshooting. The first managed node independently determines the managed node requiring interconnection and collaboration to handle the target service as the second managed node. Then, the first managed node sends a third request to request interconnection and collaboration with the second managed node. Alternatively, the first managed node sends a third request to request the primary management node to determine the managed node requiring interconnection and collaboration to handle the target service.

[0231] S1202, the master management node sends a third response message to the first managed node. Correspondingly, the first managed node receives the third response message from the master management node.

[0232] The third response information includes information associated with the second managed node.

[0233] In one possible implementation, the implementation process of S1202 includes: when the third request information is used to request interconnection and collaboration with the second managed node, the master management node can determine the information associated with the second managed node from the first management group, add the information associated with the second managed node to the third response information, and then send the third response information including the information associated with the second managed node.

[0234] In another possible implementation, the implementation process of S1202 includes: when the third request information is used to request the master management node to determine the managed node of the interconnection collaboration, the master management node can determine the managed node of the interconnection collaboration (for example, the managed node of the interconnection collaboration is the second managed node), determine the information associated with the managed node of the interconnection collaboration from the first management group, add the information associated with the managed node of the interconnection collaboration to the third response information, and then send the third response information including the information associated with the managed node of the interconnection collaboration.

[0235] Optionally, the information associated with the second managed node in the third response message can carry a validity period.

[0236] In the embodiments shown in S1201-S1202 above, the first managed node is not configured with a first management group, meaning that the first management group does not have the ability to determine the information associated with the second managed node on its own. In this case, the first managed node can send a third request message, requesting the main management node to return the information associated with the second managed node.

[0237] In some embodiments, after S1202, the process of interconnection and collaboration between the first managed node and the second managed node can be implemented through the following S1203-S1204.

[0238] S1203, the first managed node sends a fifth request message to the second managed node. Correspondingly, the second managed node receives the fifth request message from the first managed node.

[0239] The fifth request information is used to request the second managed node to interconnect and collaborate with the first managed node. The fifth request information includes information associated with the second managed node, which includes system information and authentication information of the system corresponding to the second managed node.

[0240] It should be noted that the second managed node can verify the fifth request information based on the information associated with the second managed node. After the verification is successful, it responds to the fifth request information and quickly forms a network with the first managed node to interconnect and collaboratively process the target business.

[0241] S1204. The second managed node sends the interconnection and coordination results to the first managed node. Correspondingly, the first managed node receives the interconnection and coordination results from the second managed node.

[0242] In one example, the interconnection and collaboration result can be whether the second managed node is interconnected and collaborates with the first managed node.

[0243] In the embodiments shown in S1203-S1204 above, the first managed node can request the second managed node to perform interconnection and cooperation, and learn about the interconnection and cooperation results.

[0244] In some embodiments, if the validity period of the historical information associated with the second managed node obtained by the first managed node expires, such as Figure 12 As shown, the process of the master management node updating the information associated with the second managed node may include the following steps S1205-S1206.

[0245] S1205. If the validity period of the information associated with the second managed node expires, the first managed node sends a fourth request message to the master management node. Accordingly, the master management node receives the fourth request message from the first managed node.

[0246] The fourth request information is used to request an update of the information associated with the second managed node.

[0247] In one possible implementation, the implementation process of S1205 includes: as follows Figure 13 As shown, taking the example of the first managed node sending a third response message in S1202 containing the validity period of the information associated with the second managed node. After a preset timeout following the completion of S1204, the first managed node again initiates the target service. Based on the information associated with the second managed node obtained in step S1202, it requests the second managed node to interconnect and coordinate with the first managed node. The second managed node returns an indication to the first managed node that the validity period of the information associated with the second managed node has expired. Subsequently, the first managed node sends a fourth request message to request an update to the information associated with the second managed node.

[0248] For example, consider a scenario where the information associated with the second managed node has a validity period of 10 days. One month after the execution of step S1204, the first managed node again receives the target business request. Based on the 10-day validity period of the information associated with the second managed node obtained in step S1202, it requests the second managed node to interconnect and coordinate with the first managed node. The second managed node returns an indication to the first managed node that the validity period of the information associated with it has expired. Subsequently, the first managed node sends a fourth request to request an update to the information associated with the second managed node.

[0249] S1206, The master management node sends a fourth response message to the first managed node. Correspondingly, the first managed node receives the fourth response message from the master management node.

[0250] The fourth response information includes the updated information associated with the second managed node.

[0251] In one example, such as Figure 13 As shown, the updated information associated with the second managed node included in the fourth response information carries a validity period.

[0252] Furthermore, after S1206, the first managed node can re-initiate an interconnection and collaboration request to the second managed node based on the updated information associated with the second managed node.

[0253] In the embodiments shown in S1205-S1206 above, the first managed node can request to update the information associated with the second managed node when the validity period of the information associated with the second managed node expires, so as to ensure the realization of interconnection and collaboration between the two.

[0254] Example 4

[0255] As one possible embodiment of this application, such as Figure 14 As shown, the process by which the first managed node determines to interconnect and collaborate with the second managed node can be implemented through the following steps S1401-S1403.

[0256] S1401, the master management node sends a first management group to the first managed node and / or the second managed node. Accordingly, the first managed node receives the first management group from the master management node, and / or the second managed node receives the first management group from the master management node.

[0257] In one possible implementation, the process of S1401 includes: the master management node can send the first management group to one or more managed nodes in the first management group.

[0258] In one example, if the first managed node has joined the first management group and the second managed node has not joined the first management group, the master management node can send the first management group to the first managed node, and then send the first management group to the second managed node after the second managed node joins the first management group.

[0259] Additional notes: The master management node can send the first management group to each managed node in the first management group.

[0260] S1402, The first managed node is determined to be interconnected and coordinated with the second managed node in the first management group.

[0261] In one possible implementation, S1402 includes the following process: when the first managed node needs to interconnect and coordinate with other managed nodes for a target service, the first managed node can determine on its own whether to interconnect and coordinate with the second managed node in the first management group to handle the target service.

[0262] In one example, if a device in the system corresponding to the first managed node experiences a service failure, it is necessary to interconnect and collaborate with the systems corresponding to other managed nodes to achieve cross-domain troubleshooting. The first managed node independently determines the managed node that needs to be interconnected and collaborated with to handle the target service as the second managed node.

[0263] S1403, The first managed node determines the information associated with the second managed node from the first management group.

[0264] Understandably, since the first managed node has already been configured with a first management group in step S1401, it can determine the information associated with the second managed node from its own configured first management group. Thus, even if the communication link between the first and second managed nodes fails when the first managed node needs to interconnect and collaborate, the information associated with the second managed node can still be determined, ensuring the interconnection and collaboration between the two nodes.

[0265] In the embodiments shown in S1401-S1403 above, the first managed node can be configured with a first management group. Then, when it is necessary to interconnect and coordinate with the second managed node, the information associated with the second managed node can be determined based on its own configured first management group.

[0266] In some embodiments, after S1403, the process of interconnection and collaboration between the first managed node and the second managed node can be implemented through the following S1404-S1405.

[0267] S1404, The first managed node sends a fifth request to the second managed node. Correspondingly, the second managed node receives the fifth request from the first managed node.

[0268] The fifth request information is used to request the second managed node to interconnect and collaborate with the first managed node. The fifth request information includes information associated with the second managed node, which includes system information and authentication information of the system corresponding to the second managed node.

[0269] Optionally, the specific implementation process of S1404 can be referred to the embodiment shown in S1203, and will not be repeated here.

[0270] S1405, the second managed node sends the interconnection and coordination result to the first managed node. Correspondingly, the first managed node receives the interconnection and coordination result from the second managed node.

[0271] Optionally, the specific implementation process of S1405 can be referred to the embodiment shown in S1204, and will not be repeated here.

[0272] The method provided in this application has been described above. In addition, this application also provides a communication device for implementing the functions described in the above method embodiments.

[0273] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0274] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0275] communication device Figure 15 A schematic diagram of a communication device 150 is shown. The communication device 150 includes a processing module 1501 and a transceiver module 1502. The communication device 150 can be used to implement the functions of the aforementioned master management node or first managed node.

[0276] In some embodiments, the communication device 150 may further include a storage module ( Figure 15 (Not shown in the image) is used to store program instructions and data.

[0277] In some embodiments, the transceiver module 1502, also referred to as a transceiver unit, is used to implement sending and / or receiving functions. The transceiver module 1502 may consist of a transceiver circuit, a transceiver, a transceiver unit, or a communication interface.

[0278] In some embodiments, the transceiver module 1502 may include a receiving module and a sending module, respectively configured to perform the receiving and sending steps performed by the master management node or the first managed node in the above method embodiments, and / or other processes to support the technology described herein; the processing module 1501 may be configured to perform the processing steps performed by the master management node or the first managed node in the above method embodiments, and / or other processes to support the technology described herein.

[0279] When the communication device 150 is used to implement the functions of the master management node:

[0280] In one possible implementation, the transceiver module 1502 is configured to: receive first information from a first managed node, the first information being used to instruct the first managed node to agree to join a first management group, or to request the first managed node to join the first management group; the transceiver module 1502 is further configured to: receive second information from a second managed node, the second information being used to instruct the second managed node to agree to join the first management group, or to request the second managed node to join the first management group; the processing module 1501 is configured to determine a first management group based on the first information and the second information, the first management group including information associated with the first managed node and information associated with the second managed node, the first management group being used for interconnection and collaboration between the system corresponding to the first managed node and the system corresponding to the second managed node.

[0281] In one possible implementation, when the first information is used to indicate that the first managed node agrees to join the first management group, the first information is a first response information; the transceiver module 1502 is further configured to: send a first request information to the first managed node, the first request information being used to request the first managed node to join the first management group.

[0282] In one possible implementation, the transceiver module 1502 is further configured to: receive a third request message from the first managed node; the third request message is used to request interconnection and collaboration with the second managed node; and send a third response message, the third response message including information associated with the second managed node.

[0283] In one possible implementation, the transceiver module 1502 is further configured to: receive a fourth request message from the first managed node; the fourth request message is used to request an update of the information associated with the second managed node; and send a fourth response message, the fourth response message including the updated information associated with the second managed node.

[0284] In one possible implementation, the transceiver module 1502 is further configured to: send a first management group to the first managed node and / or the second managed node.

[0285] When the communication device 150 is used to implement the functions of the first managed node:

[0286] In one possible implementation, the transceiver module 1502 is configured to: receive a first request message from the master management node, the first request message being used to request a first managed node to join a first management group; and send a first response message, the first response message being used to instruct the first managed node to agree to join the first management group, the first management group including information associated with the first managed node and information associated with a second managed node, wherein the first managed node and the second managed node correspond to different systems, and the first management group is used for interconnection and collaboration between the system corresponding to the first managed node and the system corresponding to the second managed node.

[0287] In one possible implementation, the transceiver module 1502 is configured to: send a second request message, the second request message being used to request the first managed node to join the first management group; receive a second response message, the second response message being used to instruct the master management node to agree to the first managed node joining the first management group; the first management group includes information associated with the first managed node and information associated with the second managed node, wherein the first managed node and the second managed node correspond to different systems, and the first management group is used for interconnection and collaboration between the system corresponding to the first managed node and the system corresponding to the second managed node.

[0288] In one possible implementation, the transceiver module 1502 is further configured to: send a third request message to the master management node, the third request message being used to request interconnection and collaboration with the second managed node; and receive a third response message from the master management node, the third response message including information associated with the second managed node.

[0289] In one possible implementation, the transceiver module 1502 is further configured to: send a fourth request message to the master management node when the validity period of the information associated with the second managed node expires; the fourth request message is used to request an update of the information associated with the second managed node; receive a fourth response message from the master management node; the fourth response message includes the updated information associated with the second managed node.

[0290] In one possible implementation, the transceiver module 1502 is further configured to: receive a first management group from the master management node.

[0291] In one possible implementation, the processing module 1501 is configured to: determine a second managed node to be interconnected and coordinated with in the first management group; and determine information associated with the second managed node from the first management group.

[0292] In one possible implementation, the transceiver module 1502 is further configured to: send a fifth request to the second managed node, the fifth request being used to request the second managed node to interconnect and collaborate with the first managed node, the fifth request including information associated with the second managed node, the information associated with the second managed node including system information and authentication information of the system corresponding to the second managed node; and receive the interconnection and collaboration result from the second managed node.

[0293] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0294] In this application, the communication device 150 can be presented in an integrated manner, divided into various functional modules. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.

[0295] In some embodiments, when Figure 15 When the communication device 150 is a chip or chip system, the function / implementation process of the transceiver module 1502 can be implemented through the input / output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 1501 can be implemented through the processor (or processing circuit) of the chip or chip system.

[0296] Since the communication device 150 provided in this embodiment can execute the above method, the technical effects it can achieve can be referred to the above method embodiment, and will not be repeated here.

[0297] As a possible product form, the master management node or the first managed node described in the embodiments of this application can be implemented using the following: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[0298] As another possible product form, the main management node and the first managed node in this application can adopt... Figure 16 The shown composition structure, or including Figure 16 The components shown. Figure 16This application provides a schematic diagram of the composition of a communication device 1600, which can be a master management node or a chip or system-on-a-chip in the master management node; or, it can be a first managed node or a module, chip or system-on-a-chip in the first managed node.

[0299] like Figure 16 As shown, the communication device 1600 includes at least one processor 1601 and at least one communication interface. Figure 16 (This is merely an example illustration, using a communication interface 1604 and a processor 1601 as examples. Optionally, the communication device 1600 may also include a communication bus 1602 and a memory 1603.)

[0300] Processor 1601 can be a general-purpose central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a PLD, or any combination thereof. Processor 1601 can also be other devices with processing functions, such as circuits, devices, or software modules, without limitation.

[0301] The communication bus 1602 is used to connect different components in the communication device 1600, enabling communication between them. The communication bus 1602 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 16 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0302] Communication interface 1604 is used for communicating with other devices or communication networks. For example, communication interface 1604 can be a module, circuit, transceiver, or any device capable of communication. Optionally, communication interface 1604 can also be an input / output interface located within processor 1601, used to implement signal input and signal output for the processor.

[0303] The memory 1603 may be a device with storage function, used to store instructions and / or data. The instructions may be computer programs.

[0304] For example, the memory 1603 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and / or instructions; it may also be a random access memory (RAM) or other type of dynamic storage device capable of storing information and / or instructions; it may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, etc., without limitation.

[0305] It should be noted that the memory 1603 can exist independently of the processor 1601, or it can be integrated with the processor 1601. The memory 1603 can be located inside or outside the communication device 1600, without limitation. The processor 1601 can be used to execute the instructions stored in the memory 1603 to implement the methods provided in the following embodiments of this application.

[0306] As an optional implementation, the communication device 1600 may also include an output device 1605 and an input device 1606. The output device 1605 communicates with the processor 1601 and can display information in various ways. For example, the output device 1605 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 1606 communicates with the processor 1601 and can receive user input in various ways. For example, the input device 1606 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0307] In some embodiments, the hardware implementation will be apparent to those skilled in the art as described above. Figure 15 The communication device 150 shown can be adopted Figure 16 The communication device shown is in the form of 1600.

[0308] As an example, Figure 16 The function / implementation process of the processing module 1501 can be achieved through... Figure 16 The processor 1601 in the communication device 1600 shown calls computer execution instructions stored in memory 1603 to achieve this. Figure 15 The function / implementation process of the transceiver module 1502 can be obtained through Figure 16 This is achieved through the communication interface 1604 in the communication device 1600 shown.

[0309] It should be noted that, Figure 16 The structure shown does not constitute a specific limitation on the master management node or the first managed node. For example, in other embodiments of this application, the master management node or the first managed node may include more or fewer components than shown, or combine some components, or split some components, or have different component arrangements. The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0310] In some embodiments, this application also provides a communication device, which includes a processor for implementing the methods in any of the above method embodiments.

[0311] As one possible implementation, the communication device also includes a memory. This memory stores necessary computer programs and data. The computer program may include instructions, which a processor can invoke to instruct the communication device to execute the methods described in any of the above method embodiments. Alternatively, the memory may not be present in the communication device.

[0312] As another possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, used to receive computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmit them to the processor.

[0313] As another possible implementation, the communication device also includes a communication interface for communicating with modules outside the communication device.

[0314] It is understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete devices. This application does not specifically limit this.

[0315] This application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a computer, implements the functions of any of the above-described method embodiments.

[0316] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0317] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0318] It is understood that the systems, apparatuses, and methods described in this application can also be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0319] The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. The components shown as units may or may not be physical units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0320] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0321] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive (SSD)). In this embodiment, the computer may include the aforementioned apparatus.

[0322] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0323] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of this application. Accordingly, this specification and drawings are merely illustrative descriptions of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, Applied to the primary management node, the method includes: Receive first information from the first managed node, the first information being used to instruct the first managed node to agree to join the first management group, or to request the first managed node to join the first management group; Receive second information from the second managed node, the second information being used to instruct the second managed node to agree to join the first management group, or to request the second managed node to join the first management group; Based on the first information and the second information, the first management group is determined. The first management group includes information associated with the first managed node and information associated with the second managed node. The first management group is used for interconnection and collaboration between the system corresponding to the first managed node and the system corresponding to the second managed node.

2. The method according to claim 1, characterized in that, The first information is used to indicate that the first managed node agrees to join the first management group, and the first information is a first response information; the method further includes: Send a first request message to the first managed node, the first request message being used to request the first managed node to join the first management group.

3. The method according to claim 2, characterized in that, The first request information includes the first authentication information and the first system information associated with the first managed node; The information associated with the first managed node includes first authentication information and first system information associated with the first managed node, or includes second authentication information and second system information associated with the first managed node; the first authentication information and the second authentication information are authentication information for different systems; the first system information and the second system information are system interface information opened for different systems.

4. The method according to claim 3, characterized in that, The first request information further includes at least one of the following: the identifier of the first management group, the system information of the first system, and the authentication information of the first system; and / or, The first response information includes at least one of the following: system information of the first system, authentication information of the first system; The first system is the system where the main management node is located.

5. The method according to claim 1, characterized in that, When the first information is used to request the first managed node to join the first management group, the first information is a second request information, and the method further includes: A second response message is sent to the first managed node, the second response message indicating that the first managed node is agreed to join the first management group.

6. The method according to claim 5, characterized in that, The second request information includes the first authentication information and the first system information associated with the first managed node, and the information associated with the first managed node includes the first authentication information and the first system information associated with the first managed node; Alternatively, the second request information includes the first authentication information, the first system information, the second authentication information, and the second system information associated with the first managed node, and the information associated with the first managed node includes the second authentication information and the second system information associated with the first managed node; the first authentication information and the second authentication information are authentication information for different systems; the first system information and the second system information are system interface information opened for different systems.

7. The method according to claim 6, characterized in that, The second request information also includes at least one of the following: the identifier of the first management group, the system information of the first system, and the authentication information of the first system; and / or, The second response information includes at least one of the following: first authentication information and first system information associated with the first managed node.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: Receive a third request from the first managed node; the third request is used to request interconnection and collaboration with the second managed node. Send a third response message, which includes information associated with the second managed node.

9. The method according to claim 8, characterized in that, The method further includes: Receive a fourth request from the first managed node; the fourth request is used to request an update of the information associated with the second managed node. Send a fourth response message, which includes updated information associated with the second managed node.

10. The method according to any one of claims 1-7, characterized in that, The method further includes: Send the first management group to the first managed node and / or the second managed node.

11. The method according to any one of claims 1-10, characterized in that, The first management group also includes the validity period of the information associated with the first managed node, and / or the validity period of the information associated with the second managed node.

12. The method according to any one of claims 1-11, characterized in that, The information associated with the first managed node includes at least one of the following: node identifier, system information of the system corresponding to the first managed node, or authentication information of the system corresponding to the first managed node.

13. A communication method, characterized in that, Applied to the first managed node, the method includes: Receive a first request message from the master management node, the first request message being used to request the first managed node to join the first management group; Send a first response message, which is used to indicate that the first managed node agrees to join the first management group. The first management group includes information associated with the first managed node and information associated with the second managed node. The first managed node and the second managed node correspond to different systems. The first management group is used for interconnection and collaboration between the system corresponding to the first managed node and the system corresponding to the second managed node.

14. The method according to claim 13, characterized in that, The first request information includes the first authentication information and the first system information associated with the first managed node; The information associated with the first managed node includes first authentication information and first system information associated with the first managed node, or second authentication information and second system information associated with the first managed node; the first authentication information and the second authentication information are authentication information for different systems; the first system information and the second system information are system interface information opened for different systems.

15. The method according to claim 14, characterized in that, The first request information further includes at least one of the following: the identifier of the first management group, the system information of the first system, and the authentication information of the first system; and / or, The first response information includes at least one of the following: system information of the first system, authentication information of the first system; The first system is the system where the main management node is located.

16. A communication method, characterized in that, Applied to the first managed node, the method includes: Send a second request message, which is used to request the first managed node to join the first management group; The system receives a second response message, which instructs the master management node to agree to the first managed node joining the first management group. The first management group includes information associated with the first managed node and information associated with the second managed node. The first managed node and the second managed node correspond to different systems. The first management group is used for interconnection and collaboration between the system corresponding to the first managed node and the system corresponding to the second managed node.

17. The method according to claim 16, characterized in that, The second request information includes the first authentication information and the first system information associated with the first managed node, and the information associated with the first managed node includes the first authentication information and the first system information associated with the first managed node; Alternatively, the second request information includes the first authentication information, the first system information, the second authentication information, and the second system information associated with the first managed node, and the information associated with the first managed node includes the second authentication information and the second system information associated with the first managed node; the first authentication information and the second authentication information are authentication information for different systems; the first system information and the second system information are system interface information opened for different systems.

18. The method according to claim 17, characterized in that, The second request information also includes at least one of the following: the identifier of the first management group, the system information of the first system, and the authentication information of the first system; and / or, The second response information includes at least one of the following: first authentication information and first system information associated with the first managed node; The first system is the system where the main management node is located.

19. The method according to any one of claims 13-18, characterized in that, The method further includes: Send a third request message to the master management node, the third request message being used to request interconnection and collaboration with the second managed node; Receive third response information from the master management node, the third response information including information associated with the second managed node.

20. The method according to claim 19, characterized in that, The method further includes: If the validity period of the information associated with the second managed node expires, a fourth request message is sent to the main management node; the fourth request message is used to request the update of the information associated with the second managed node. Receive a fourth response message from the master management node; the fourth response message includes updated information associated with the second managed node.

21. The method according to any one of claims 13-18, characterized in that, The method further includes: Receive the first management group from the master management node.

22. The method according to claim 21, characterized in that, The method further includes: It is determined that the second managed node in the first management group needs to be interconnected and coordinated. Determine the information associated with the second managed node from the first management group.

23. The method according to any one of claims 19-22, characterized in that, The method further includes: The system requests information from the second managed node. The fifth request information is used to request the second managed node to interconnect and collaborate with the first managed node. The fifth request information includes information associated with the second managed node, which includes system information and authentication information of the system corresponding to the second managed node. Receive the interconnection and collaboration results from the second managed node.

24. The method according to any one of claims 13-23, characterized in that, The information associated with the first managed node includes at least one of the following: node identifier, system information of the system corresponding to the first managed node, and authentication information of the system corresponding to the first managed node.

25. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 1-12, or includes a module for performing the method as described in any one of claims 13-24.

26. A communication device, characterized in that, The communication device includes a processor; the processor is configured to run a computer program or instructions to cause the communication device to perform the method as described in any one of claims 1-12, or to cause the communication device to perform the method as described in any one of claims 13-24.

27. A computer-readable storage medium, characterized in that, A computer-readable storage medium stores computer instructions or programs that, when executed on a computer, cause the method described in any one of claims 1-12 to be performed, or cause the method described in any one of claims 13-24 to be performed.

28. A computer program product, characterized in that, The computer program product includes computer instructions; when some or all of the computer instructions are run on a computer, they cause the method as described in any one of claims 1-12 to be performed, or cause the method as described in any one of claims 13-24 to be performed.

Images