Control network construction method, equipment control method and corresponding device

Abstract

The present application relates to the field of computer technology, and provides a method for constructing a control network, a device control method, and a corresponding device. The method for constructing a control network includes: determining the communication connection relationship between control entities based on preset connection rules; wherein each control entity includes at least one terminal device to be controlled, and the control entity corresponds to a node in the topological structure of the control network; based on the communication connection relationship, a data transmission channel is established between the control entities to form a control network; wherein the data transmission channel corresponds to an edge between nodes in the topological structure. The control network in this method does not include a central server, and its deployment is simple and the operating cost is low. Moreover, since the control entities in the control network are all involved in the device control, the pressure on a single device is significantly reduced and the resource utilization rate is improved. Moreover, the efficiency of the control network in device control is not greatly affected by the number of terminal devices.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method for constructing a management and control network, a device management and control method, and corresponding devices. Background Art

[0002] At present, the industry generally adopts centralized control for multi-terminal management, such as the Client / Business-Server or Client / Data-Server architecture. When there are a large number of terminal devices to be managed, the centralized control method puts great pressure on the management server, and needs to consider a series of complex issues such as high concurrency, high availability, and large data storage, resulting in a significant increase in operating costs. Summary of the invention

[0003] The purpose of the embodiments of the present application is to provide a method for constructing a management and control network, a device management and control method, and a corresponding device to improve the above-mentioned technical problems.

[0004] In a first aspect, an embodiment of the present application provides a method for constructing a management and control network, comprising: determining a communication connection relationship between management and control entities based on preset connection rules; wherein each management and control entity includes at least one terminal device to be controlled, and the management and control entity corresponds to a node in a topological structure of the management and control network; based on the communication connection relationship, establishing a data transmission channel between the management and control entities to form the management and control network; wherein the data transmission channel corresponds to an edge between nodes in the topological structure.

[0005] The above method realizes the control of multiple terminal devices by building a control network between the control entities (including terminal devices). The control network does not include a central server, so it is a decentralized device control method with simple deployment and low operating costs. In addition, since the control entities in the control network are all involved in the device control, the pressure on a single device in terms of computing, storage, bandwidth, etc. is significantly reduced, and resource utilization is improved. In addition, the control network theoretically has no limit on the number of terminal devices, and even if the number of terminal devices increases, it will have little effect on its efficiency in device control.

[0006] In an implementation manner of the first aspect, the topological structure includes a plurality of basic polygons pieced together, and the nodes in the topological structure are vertices of the basic polygons.

[0007] In the above implementation, the management and control network can be constructed based on the same basic polygons (for example, triangles, quadrilaterals, hexagons, etc.), so that the topological structure of the management and control network is relatively simple, thereby facilitating the rapid construction of the management and control network and the rapid transmission of management and control information in the network.

[0008] In an implementation manner of the first aspect, the basic polygon is a hexagon.

[0009] In the above implementation, the topological structure of the management and control network is in a honeycomb shape (each hexagon is a honeycomb). This structure has high stability and the connection between nodes is very simple (each node is connected to at most three nearby nodes), which facilitates the rapid construction of the management and control network and the rapid transmission of management and control information in the network.

[0010] In an implementation manner of the first aspect, if the management and control entity includes multiple terminal devices, the multiple terminal devices constitute a secondary network of the management and control network, and a connection rule for constructing the secondary network is the same as a connection rule for constructing the management and control network.

[0011] In the above implementation, the management and control network can be constructed as a hierarchical network, so that terminal devices can be managed and controlled at different network levels, which significantly increases the flexibility and functionality of device management and control.

[0012] In an implementation manner of the first aspect, the management and control network belongs to an application layer network.

[0013] In the above implementation, the management and control network is located at the application layer, that is, how the terminal devices are connected below the application layer does not affect the construction of the management and control network, which makes the management and control of terminal devices more flexible and at the same time makes the management and control behavior have less impact on the existing connection relationship between devices (such as TCP connection).

[0014] In a second aspect, an embodiment of the present application provides a device control method, which is applied to a current control entity in a control network, wherein each control entity in the control network includes at least one terminal device to be controlled, and the control entity corresponds to a node in a topological structure of the control network, and a data transmission channel established between the control entities corresponds to an edge between nodes in the topological structure; the method comprises: obtaining control information; if the control information is generated by the current control entity, sending the control information to an adjacent control entity; if the control information is generated by the current control entity,

[0015] If the control information is received from the source control entity, the control information is sent to adjacent control entities other than the source control entity; wherein the adjacent control entity refers to a control entity with which a data transmission channel is established with the current control entity.

[0016] The above method realizes the control of multiple terminal devices by building a control network between control entities (including terminal devices). First, the control network does not include a central server, so it is a

[0017] The decentralized device control method is simple to deploy and has low operating costs. Secondly, since all control entities in the control network participate in device control, the pressure on a single device in terms of computing, storage, bandwidth, etc. is significantly reduced, and resource utilization is improved. Finally, in this control network, control entities can use pre-established data channels to simply and quickly spread control information, thereby efficiently completing the control of all network devices. Even if the number of terminal devices increases, it will not have much impact on their efficiency in device control.

[0018] In an implementation manner of the second aspect, the control information includes data and / or policies, and the method further includes: determining whether a version number of the data and / or policies in the control information is the same as a version number of the local data and / or policies of the current control entity; if the version numbers are different, updating the local data and / or policies of the current control entity using the data and / or policies in the control information.

[0019] 0 The above implementation method is for the case where the control information includes data and / or policies. The control entity

[0020] By comparing the version numbers of data and / or policies, it is possible to quickly determine whether to update local data and / or policies. The logic for processing data and / or policies is very simple, so that data and / or policy updates can be completed efficiently across the entire network.

[0021] In an implementation manner of the second aspect, the management and control information includes tasks, and the method further includes: executing the tasks in the management and control information.

[0022] In the above implementation, when the control information includes tasks, the control entity can directly execute the tasks, thereby efficiently completing the execution of specific tasks in the entire network.

[0023] In an implementation of the second aspect, the task in the control information is a task that needs to return a result, and executing the task in the control information includes: executing the task in the control information and obtaining an execution result; the method also includes: sending the execution result to the source control entity.

[0024] In the above implementation, for situations where tasks need to return results (for example, statistical tasks need to return statistical results), each management entity only needs to return the execution results to the source management entity according to its own task acquisition path, and eventually all execution results will be aggregated to the management entity that originally generated the task, thereby completing the collection of task execution results. This method of collecting task execution results is simple and efficient.

[0025] In an implementation of the second aspect, the control information includes a remote control request, and obtaining the control information includes: receiving the control information from the source control entity; the method also includes: determining whether the current control entity is the target control entity to be controlled by the remote control request in the control information; if the current control entity is the target control entity, responding to the remote control request to accept remote control; if the current control entity is not the target control entity, executing the step of sending the control information to an adjacent control entity other than the source control entity.

[0026] The above implementation method targets the situation where the management and control information includes a remote control request. The management and control entity can quickly determine whether to respond to the remote control request or continue to forward the remote control request by judging whether the target management and control entity to be controlled by the remote control request is itself. The logic for processing remote control requests is very simple, so that single-point control of the management and control entity can be efficiently completed, thereby improving the user's device management experience.

[0027] In an implementation of the second aspect, the topological structure includes a plurality of hexagons pieced together, the nodes in the topological structure are the vertices of the hexagons, and the adjacent management and control entities refer to at most three management and control entities that have established data transmission channels with the current management and control entity.

[0028] In the above implementation, the topological structure of the management and control network is honeycomb-shaped (each hexagon is a honeycomb). This structure is highly stable and the connections between nodes are very simple (each node is connected to at most three nearby nodes), which makes the information forwarding logic of each management and control entity simple and efficient.

[0029] In a third aspect, an embodiment of the present application provides a device for constructing a management and control network, comprising: a connection relationship determination module, used to determine the communication connection relationship between management and control entities based on preset connection rules; wherein each management and control entity includes at least one terminal device to be controlled, and the management and control entity corresponds to a node in the topological structure of the management and control network; a connection relationship establishment module, used to establish a data transmission channel between the management and control entities based on the communication connection relationship to form the management and control network; wherein the data transmission channel corresponds to an edge between nodes in the topological structure.

[0030] In a fourth aspect, an embodiment of the present application provides a device control device, which is configured in a current control entity in a control network, each control entity in the control network includes at least one terminal device to be controlled, the control entity corresponds to a node in a topological structure of the control network, and a data transmission channel established between the control entities corresponds to an edge between nodes in the topological structure; the device includes: an information acquisition module, used to obtain control information; an information forwarding module, used to send the control information to an adjacent control entity when the control information is generated by the current control entity, and to send the control information to an adjacent control entity other than the source control entity when the control information is received by the current control entity from a source control entity; wherein the adjacent control entity refers to a control entity with which a data transmission channel is established.

[0031] In a fifth aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, which, when read and executed by a processor, execute the method provided by the first aspect, the second aspect, or any possible implementation of these two aspects.

[0032] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are read and executed by a processor, the method provided by the first aspect, the second aspect, or any possible implementation of these two aspects is executed.

[0033] In the seventh aspect, an embodiment of the present application provides an electronic device, comprising: a memory and a processor, wherein the memory stores computer program instructions, and when the computer program instructions are read and run by the processor, the method provided by the first aspect, the second aspect, or any possible implementation of these two aspects is executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0035] Figure 1 The following illustrates the steps that may be included in the method for constructing a management and control network provided in an embodiment of the present application;

[0036] Figure 2 The topological structure that the management and control network provided in the embodiment of the present application may have is shown;

[0037] Figure 3 The following are the steps that may be included in the device control method provided in the embodiment of the present application;

[0038] Figure 4(A) to Figure 4(C) The process of propagating control information in the embodiment of the present application is shown;

[0039] Figure 5 The functional modules that may be included in the device for constructing a management and control network provided in an embodiment of the present application are shown;

[0040] Figure 6 The functional modules that may be included in the equipment control device provided in the embodiment of the present application are shown;

[0041] Figure 7 The structure of an electronic device provided by an embodiment of the present application is shown. DETAILED DESCRIPTION

[0042] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

[0043] The terms "comprises," "comprising," or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0044] Figure 1 The following diagram shows the steps that may be included in the method for constructing a control network provided in an embodiment of the present application. The method may be executed by a terminal device to be controlled (or a terminal device participating in constructing a control network). Figure 7 The possible structures of these terminal devices are shown. For details, please refer to the following Figure 7 Reference Figure 1 , the construction methods of the control network include:

[0045] Step S110: Determine the communication connection relationship between the managed entities based on the preset connection rules.

[0046] Step S120: Based on the communication connection relationship between the management and control entities, a data transmission channel is established between the management and control entities to form a management and control network.

[0047] Before introducing the construction method of the control network, let's first explain the purpose and composition of the control network:

[0048] The management and control network is used for the management and control of multiple terminal devices. Terminal devices generally refer to devices on the user side. Terminal devices may be physical devices, such as PCs, laptops, tablets, mobile phones, wearable devices, home appliances, robots, industrial equipment, vehicles, etc., or they may be virtual devices, such as virtual machines, virtualized containers, etc.

[0049] The management and control network is composed of management and control entities that have established data transmission channels with each other. Each management and control entity may include one or more terminal devices to be controlled. If a management and control entity includes multiple terminal devices, then optionally, one of these terminal devices can be selected to communicate with the outside of the management and control entity, so that the management and control entity looks like a terminal device from the outside. As for which terminal devices are to be classified as one management and control entity, it can be determined according to demand. For example, all terminal devices in a local area network can be classified as one management and control entity, but this is not a mandatory requirement. Before executing step S110, the management and control entities used to construct the management and control network may have been determined.

[0050] Each control entity in the control network will establish a data transmission channel with one or more other control entities. These data transmission channels can be used to transmit control information in order to achieve device control. The data transmission channel between control entities is established between the terminal devices contained in the control entities. For example, if two control entities only contain one terminal device, the data transmission channel can be established between the two terminal devices contained in the two control entities; for another example, if one control entity contains one terminal device and the other control entity contains multiple terminal devices, one terminal device can be selected from the terminal devices contained in the latter control entity as a terminal device for external communication, and a data transmission channel can be established with the terminal device contained in the former control entity, and so on.

[0051] The management and control network has a specific topological structure, which is composed of nodes and edges connecting the nodes. Each management and control entity in the management and control network corresponds to a node in its topological structure, and the data transmission channel established between every two management and control entities in the management and control network corresponds to an edge between the nodes in its topological structure.

[0052] Figure 2 Figure 2 shows a possible topology of a control network. Figure 2 The control network can be called a "honeycomb network", and its topology consists of multiple hexagons (each hexagon is a honeycomb) stitched together, and the vertices of these hexagons are nodes in the topology. Figure 2In the figure, the gray circles represent nodes. For the nodes represented by the smaller gray circles, the corresponding control entity only includes one terminal device. For the nodes represented by the larger gray circles, the corresponding control entity includes multiple terminal devices. Note that Figure 2 Some of the hexagons are missing some vertices (such as the hexagon in the lower left corner), but in order to facilitate the display of the honeycomb structure of the management and control network, these hexagons are still completed with dotted edges. It should be understood that these dotted edges do not exist in the actual topological structure, and there are no real nodes at the intersection of these dotted edges. It is reasonable for the topological structure to contain some incomplete hexagons, because the number of nodes depends on the number of management and control entities, and it is not necessarily possible to ensure that every hexagon is complete.

[0053] Combine the following Figure 2 The topological structure in the figure is used to illustrate the construction process of the control network. Before building the control network, you need to determine the topological structure of the control network, such as Figure 2 According to the determined topology, connection rules between control entities can be set. Figure 2 It can be seen that each node in the topological structure of the honeycomb network is connected to at most three other nodes through edges. Furthermore, in order to make the explanation of the connection rules not too complicated, only the case where each node is connected to three other nodes is considered (the other cases can be analyzed similarly), so that the connection rules can be set: connect each control entity to three other control entities.

[0054] According to the guidance of this connection rule, in step S110, for any control entity A, 3-x control entities can be selected from the remaining control entities to determine whether there is a communication connection relationship between the control entity A and these 3-x control entities. Wherein, x is an integer between 0 and 2, and x represents the number of control entities that have been determined to have a communication connection relationship with the control entity A. There is no limit to the way of selecting 3-x control entities, for example, it can be random selection, nearby selection, etc. In step S120, a data transmission channel is established between the control entity A and the 3-x control entities, so that the communication connection relationship determined in step S110 can be realized. After all control entities are processed in the same way as the control entity A, the control network is constructed.

[0055] It should be understood that as the topological structure of the control network to be constructed is different, the connection rules in step S110 should also be adjusted accordingly. For example, if the topological structure of the control network is composed of multiple rectangles, the connection rules may include: connecting each control entity to four other control entities, and so on.

[0056] The construction of the control network can be a single-point diffusion type, for example:

[0057] (1) Randomly select one from all the regulated entities. Assume that regulated entity A is selected.

[0058] (2) Randomly select three control entities B, C, and D from the remaining control entities, and establish data transmission channels between B, C, D and A respectively.

[0059] (3) For the control entity B, two control entities E and F are randomly selected from the remaining control entities (because B is already connected to A, so two are enough), and data transmission channels are established between E and F and B respectively; at the same time, for the control entity C, two control entities G and H are randomly selected from the remaining control entities (because C is already connected to A, so two are enough), and data transmission channels are established between G and H and C respectively; at the same time, for the control entity D, two control entities I and J are randomly selected from the remaining control entities (because D is already connected to A, so two are enough), and data transmission channels are established between I and J and D respectively.

[0060] By analogy, starting from a starting point (control entity A), new control entities are continuously selected and data transmission channels are established between control entities, and finally the construction of the entire control network is completed.

[0061] Of course, single-point diffusion is not the only way to build a management and control network: for example, multi-point diffusion can be used to build a management and control network in parallel from multiple starting points to improve construction efficiency; for example, the communication connection relationship between all management and control entities can be determined first, and then all data transmission channels can be established at one time, and so on.

[0062] Brief summary Figure 1 The method in this paper realizes the control of multiple terminal devices by building a control network between the control entities. The control network does not include a central server, so it is a decentralized device control method with simple deployment and low operating costs. In addition, since the control entities in the control network are all involved in the device control, the pressure on a single device in terms of computing, storage, bandwidth, etc. is significantly reduced, and resource utilization is improved. In addition, the control network theoretically has no limit on the number of terminal devices. Even if the number of terminal devices increases, since there is no performance bottleneck (such as the performance bottleneck of the central server), it has little effect on its efficiency in device control.

[0063] In the above description, we also introduced the special case of the honeycomb structure used in the control network. Since the honeycomb structure has the characteristics of high stability and very simple connections between nodes (each node is connected to at most three nearby nodes), it is convenient for the rapid construction of the control network and the rapid transmission of control information in the network.

[0064] Furthermore, in other implementations of the control network, its topological structure may include multiple basic polygons pieced together. If the basic polygon is a hexagon, then the control network is a honeycomb network. Of course, the basic polygon may also be in other shapes, such as a triangle, a quadrilateral, a pentagon, etc. The vertices of the basic polygon are nodes in the topological structure. In this implementation, since the control network is constructed based on the same geometric figure (basic polygon), the topological structure of the control network is relatively simple, which facilitates the rapid construction of the control network and the rapid transmission of control information in the network.

[0065] In the above description, it is also mentioned that the control entity may include multiple terminal devices. In this case, optionally, based on these multiple terminal devices, a secondary network of the control network can be further constructed with reference to steps S110 to S120. The connection rules used to construct the secondary network can be the same as the connection rules used to construct the control network. In other words, the topology of the secondary network and the topology of the control network can be similar (for example, both are honeycomb structures), so as to facilitate unified control of the devices. Of course, the multiple terminal devices within the control entity do not necessarily have to construct a secondary control network, or even if a secondary network is constructed, a different type of topology from the control network may be used.

[0066] Refer again Figure 2 There is a larger gray circle below the topological structure of the management and control network. The corresponding management and control entities include 10 terminal devices. These 10 terminal devices are regarded as 10 management and control entities. Referring to steps S110 to S120, a secondary network can be constructed. Its topological structure is shown in the box on the right. The secondary network is still a cellular network. Therefore, the larger gray circle can also be called a node of the corresponding secondary network.

[0067] The topology of the secondary network contains 10 nodes, each of which corresponds to a terminal device (or a control entity in the secondary network). One terminal device is selected as the device for communicating with the outside of the secondary network. The node corresponding to the device is Figure 2 It is represented by a white circle in the figure and is called an external node in the secondary network.

[0068] It should be understood that if the management and control entity in the secondary network includes multiple terminal devices, a secondary network of the secondary network can be further constructed, and the process will not be repeated.

[0069] In the above implementation, the management and control network can be constructed as a hierarchical network with several secondary networks under its jurisdiction, so that terminal devices can be managed and controlled at different network levels, which significantly increases the flexibility and functionality of device management and control.

[0070] The control network introduced above can be implemented as an application layer network, that is, how the terminal devices are connected below the application layer does not affect the construction of the control network. The control network can be set up only for one or some control applications, which makes the control of terminal devices more flexible and makes the control behavior have less impact on the existing connection relationship between devices (such as TCP connection). Of course, it is not ruled out that the control network can be implemented at other protocol layers. For example, if the control network is implemented at the transport layer, the data transmission channel between the control entities can be implemented as a TCP connection.

[0071] Figure 3 The steps that may be included in the device control method provided in the embodiment of the present application are shown. The method can be executed by any control entity in the control network. For the convenience of explanation, the control entity will be referred to as the current control entity in the following text. For the composition and construction method of the control network, please refer to the previous content and will not be repeated. Specifically, if the current control entity only includes one terminal device, the method can be executed by the terminal device; if the current control entity includes multiple terminal devices, the method can be executed by a terminal device selected from the multiple terminal devices for external communication, or it can also be executed by multiple terminal devices in cooperation. Reference Figure 3 , equipment control methods include:

[0072] Step S210: The current management and control entity obtains management and control information.

[0073] Step S220: If the control information is generated by the current control entity, the current control entity sends the control information to the adjacent control entities; if the control information is received by the current control entity from the source control entity, the current control entity sends the control information to the adjacent control entities except the source control entity.

[0074] Among them, control information generally refers to information related to device control. In the following text, examples of several types of control information that may be generated will be given, which will not be elaborated here. There are two ways for the current control entity to obtain control information: one is that the current control entity itself generates control information, for example, a user logs in to the terminal device corresponding to the current control entity to configure control information; the other is that the current control entity receives control information sent to it by other control entities. For the latter, the control entity that sends the control information can be called the source control entity.

[0075] The adjacent control entities of the current control entity refer to those control entities that have established data transmission channels with the current control entity. Intuitively, in the topological structure of the control network, there are edges connecting the nodes corresponding to the adjacent control entities and the nodes corresponding to the current control entity. In particular, since the source control entity can send control information to the current control entity, there must be a data transmission channel between the source control entity and the current control entity, so the source control entity must be an adjacent control entity of the current control entity.

[0076] Step S120 actually describes the process of propagation of control information in the control network. Since the control network does not include a central server, the control information needs to be propagated between control entities before it can be spread throughout the network, thereby achieving control over terminal devices in the entire network.

[0077] If the control information is generated by the current control entity, the adjacent control entities of the current control entity have not yet obtained the information, so the current control entity can send the control information to all adjacent control entities; if the control information is received by the current control entity from the source control entity, the source control entity has already obtained the information, so the current control entity only needs to send the control information to the adjacent control entities other than the source control entity.

[0078] You can refer to Figure 4(A) to Figure 4(C) to understand the process of control information dissemination between control entities. Figure 4(A) to Figure 4(C) The figure shows the nodes in the topological structure of the control network. However, since there is a one-to-one correspondence between the control entities and the nodes, for simplicity, the following text will directly refer to Figure 4(A) to Figure 4(C) The nodes in are called management and control entities, which is consistent with the description in steps S210 to S220.

[0079] Referring to Figure 4(A), the control information is generated by the control entity A, which is represented by a black circle, indicating that the control information has been propagated to the control entity A. Referring to Figure 4(B), the control entity A sends the control information to its adjacent control entities B, C, and D, and the control entities B, C, and D also turn black, indicating that the control information has been received. Referring to Figure 4(C), for the control entity B, it receives the control information from the control entity A, so when it propagates again, it is not necessary to send the control information to A, and it only needs to be sent to the adjacent control entities E and F. Similarly, for the control entity C, it only needs to send the control information to the adjacent control entities G and H. For the control entity D, it only needs to send the control information to the adjacent control entities I and J. The control entities E, F, G, H, I, and J all turn black, indicating that the control information has been received.

[0080] Subsequent control information can be obtained according to Figure 4(A) to Figure 4(C) The given method continues to propagate until it spreads to the entire network. This process only depends on the control entity in the control network and does not depend on additional servers.

[0081] Optionally, conditions may be set for the dissemination of control information, that is, in step S220, the current control entity will continue to disseminate the control information only when certain conditions are met, otherwise the control information will no longer be disseminated. For example, if the target recipient of the control information is the current control entity, then after the current control entity obtains the information, there is no need to continue to disseminate the information, so as to avoid wasting network resources.

[0082] Brief summary Figure 3 The method in the control network realizes the control of multiple terminal devices by building a control network between the control entities. First of all, the control network does not include a central server, so it is a decentralized device control method with simple deployment and low operating costs. Secondly, since the control entities in the control network are all involved in the device control, the pressure on a single device in terms of computing, storage, bandwidth, etc. is significantly reduced, and resource utilization is improved. Finally, in the control network, the control entities can use pre-established data channels to simply and quickly spread control information, so that the control of the entire network equipment can be completed efficiently. Even if the number of terminal devices increases, its efficiency in device control is not greatly affected.

[0083] Furthermore, if the control network also includes a secondary network, the above-mentioned device control method can also be executed in the secondary network. The process is similar to that in the control network and will not be repeated.

[0084] Based on the above embodiments, several different types of control information and corresponding processing methods adopted by the current control entity are further introduced below:

[0085] (1) Control information includes data and / or policies

[0086] After the current control entity obtains the control information, it can determine whether the version number of the data and / or policy in the control information (the version number can be carried in the control information) is the same as the version number of the local data and / or policy of the current control entity. If the version numbers are different, the current control entity can use the data and / or policy in the control information to update the local data and / or policy of the current control entity. Otherwise, the current control entity can ignore the control information and do not perform any update operation.

[0087] If the control information is generated by the current control entity itself, the current control entity may also directly execute the update of data and / or policy without performing version number comparison.

[0088] In the above implementation, the management and control entity can quickly determine whether to update local data and / or policies by comparing the version numbers of the data and / or policies. The logic for processing data and / or policies is very simple, so that the update of data and / or policies can be efficiently completed across the entire network.

[0089] (2) Management information includes tasks

[0090] After the current control entity obtains the control information, it can directly execute the tasks in the control information, so that the specific tasks can be efficiently executed in the entire network. The specific task type is not limited here, for example, it can be a computing task, a virus scanning task, etc.

[0091] In particular, some tasks need to return results. For example, data statistics tasks need to summarize the statistical results on each control entity to obtain the overall statistical results of the entire network data. For such tasks, after the current control entity executes the task in the control information, it will obtain the execution result and send the execution result to the source control entity (if the control information is generated by the current control entity itself, it does not need to be sent), where the source control entity can record when the current control entity receives the control information. After each control entity performs similar operations, the task execution results on each control entity will be reversely summarized along the propagation path of the control information to the control entity that originally generated and sent the task to the outside, thereby completing the collection of task execution results simply and efficiently.

[0092] (3) Control information includes remote control requests

[0093] A remote control request is a request from one control entity to perform single-point control on another control entity. Of course, the remote control request will eventually be implemented on the terminal device included in the control entity, that is, a request from one terminal device to perform single-point control on another terminal device. For the sake of convenience, the control entity that initiates the remote control request is called the main control entity, and the control entity that the remote control request is intended to control is called the target control entity.

[0094] Obviously, if the control information is generated by the current control entity itself, it will not remotely control itself, so the following only considers the situation where the current control entity receives the control information. After the current control entity receives the control information, it can perform the following operations:

[0095] First, determine whether the current controlled entity is the target controlled entity. As an optional solution, in the control network, each controlled entity has a unique ID, and the ID of the target controlled entity can be carried in the remote control request, so that the current controlled entity can determine whether it is the target controlled entity by comparing the ID in the remote control request with its own ID.

[0096] If the judgment result shows that the current control entity is the target control entity, the current control entity responds to the remote control request to accept the remote control of the main control entity. And because the remote control request is a single-point control, if the current control entity is the target control entity, then other control entities must not be the target control entity, so the current control entity does not need to continue to spread the control information (i.e. the conditional spread mentioned above).

[0097] If the judgment result shows that the current control entity is not the target control entity, the current control entity can send control information to adjacent control entities except the source control entity, so as to continue to spread the remote control request throughout the network until the request reaches the target control entity.

[0098] In the above implementation, the control entity can quickly determine whether to respond to the remote control request or continue to forward the remote control request by judging whether the target control entity to be controlled by the remote control request is itself. The logic of processing the remote control request is very simple, so that the single-point control function of the control entity can be efficiently completed, thereby improving the user's device control experience.

[0099] exist Figure 3 In the method, the topological structure of the control network is not limited. However, a simple topological structure is more conducive to the construction of the control network and the rapid transmission of control information. For example, the control network can adopt the honeycomb structure mentioned above, that is, its topological structure includes a plurality of hexagons stitched together, and the nodes in the topological structure are the vertices of the hexagons. At this time, the adjacent control entities in step S220 refer to at most three control entities with which a data transmission channel is established with the current control entity.

[0100] The honeycomb structure has the characteristics of high stability and very simple connections between nodes, which makes the information forwarding logic of each management and control entity simple and efficient, because each management and control entity only needs to record the connection relationship with at most three other management and control entities and forward information based on this connection relationship.

[0101] Figure 5 The following figure shows the functional modules that may be included in the device for constructing a control network provided in the embodiment of the present application. Figure 5 , the construction device 300 of the control network includes:

[0102] A connection relationship determination module 310 is used to determine the communication connection relationship between the control entities based on a preset connection rule; wherein each control entity includes at least one terminal device to be controlled, and the control entity corresponds to a node in the topological structure of the control network;

[0103] The connection relationship establishing module 320 is used to establish a data transmission channel between the management and control entities based on the communication connection relationship to form the management and control network; wherein the data transmission channel corresponds to an edge between nodes in the topological structure.

[0104] In an implementation of the device 300 for constructing a management and control network, the topological structure includes a plurality of basic polygons pieced together, and the nodes in the topological structure are vertices of the basic polygons.

[0105] In one implementation of the device 300 for constructing a management and control network, the basic polygon is a hexagon.

[0106] In one implementation of the device 300 for constructing a management and control network, if the management and control entity includes multiple terminal devices, the multiple terminal devices constitute a secondary network of the management and control network, and the connection rules used to construct the secondary network are the same as the connection rules used to construct the management and control network.

[0107] In one implementation of the device 300 for constructing a management and control network, the management and control network belongs to an application layer network.

[0108] The implementation principle and technical effects of the device 300 for constructing a management and control network provided in the embodiment of the present application have been introduced in the aforementioned method embodiment. For the sake of brief description, for matters not mentioned in the device embodiment, reference may be made to the corresponding contents in the method embodiment.

[0109] Figure 6 The functional modules that may be included in the device control device provided in the embodiment of the present application are shown. The device control device is configured in the current control entity in the control network, each control entity in the control network includes at least one terminal device to be controlled, the control entity corresponds to a node in the topological structure of the control network, and the data transmission channel established between the control entities corresponds to the edge between the nodes in the topological structure. Figure 6 , the equipment control device 400 includes:

[0110] Information acquisition module 410, used to acquire management and control information;

[0111] An information forwarding module 420, configured to send the control information to an adjacent control entity when the control information is generated by the current control entity, and to send the control information to an adjacent control entity other than the source control entity when the control information is received by the current control entity from a source control entity;

[0112] The adjacent control entity refers to a control entity with which a data transmission channel is established.

[0113] In an implementation of the device management and control apparatus 400, the management and control information includes data and / or policies, and the apparatus further includes:

[0114] The first information processing module is used to determine whether the version number of the data and / or policy in the control information is the same as the version number of the local data and / or policy of the current control entity; and, when the version numbers are different, to update the local data and / or policy of the current control entity using the data and / or policy in the control information.

[0115] In an implementation of the device control apparatus 400, the control information includes tasks, and the apparatus further includes:

[0116] The second information processing module is used to execute the tasks in the management and control information.

[0117] In an implementation of the device control apparatus 400, the task in the control information is a task that needs to return a result, and the second information processing module executes the task in the control information, including: executing the task in the control information and obtaining an execution result;

[0118] The second information processing module is further used to send the execution result to the source control entity.

[0119] In an implementation of the device control apparatus 400 , the control information includes a remote control request, and the information acquisition module 410 acquires the control information, including: receiving the control information from the source control entity;

[0120] The device also includes:

[0121] The third information processing module is used to determine whether the current control entity is the target control entity to be controlled by the remote control request in the control information; and, when the current control entity is the target control entity, respond to the remote control request to accept remote control; and, when the current control entity is not the target control entity, execute the step of sending the control information to adjacent control entities other than the source control entity.

[0122] In one implementation of the equipment management and control device 400, the topological structure includes multiple hexagons pieced together, the nodes in the topological structure are the vertices of the hexagons, and the adjacent management and control entities refer to at most three management and control entities that have established data transmission channels with the current management and control entity.

[0123] The equipment control device 400 provided in the embodiment of the present application, its implementation principle and the technical effects produced have been introduced in the aforementioned method embodiment. For the sake of brief description, for matters not mentioned in the device embodiment, reference may be made to the corresponding contents in the method embodiment.

[0124] Figure 7 FIG. 5 shows a possible structure of an electronic device 500 provided in an embodiment of the present application. Figure 7 The electronic device 500 includes: a processor 510, a memory 520 and a communication interface 530. These components are interconnected and communicate with each other through a communication bus 540 and / or other forms of connection mechanisms (not shown).

[0125] Among them, the processor 510 includes one or more (only one is shown in the figure), which can be an integrated circuit chip with signal processing capabilities. The above-mentioned processor 510 can be a general-purpose processor, including a central processing unit (CPU), a micro control unit (MCU), a network processor (NP) or other conventional processors; it can also be a dedicated processor, including a neural network processor (NPU), a graphics processor (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. In addition, when there are multiple processors 510, some of them can be general-purpose processors and the other part can be dedicated processors.

[0126] The memory 520 includes one or more (only one is shown in the figure), which may be, but not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), etc. The processor 510 and other possible components may access the memory 520 and read and / or write data therein.

[0127] In particular, one or more computer program instructions may be stored in the memory 520, and the processor 510 may read and execute these computer program instructions to implement the management and control network construction method and / or device management and control method provided in the embodiments of the present application.

[0128] The communication interface 530 includes one or more (only one is shown in the figure), which can be used to communicate directly or indirectly with other devices to exchange data. The communication interface 530 can include an interface for wired and / or wireless communication.

[0129] Understandably, Figure 7 The structure shown is for illustration only. The electronic device 500 may also include Figure 7 More or fewer components as shown, or with Figure 7 Different structures are shown. Figure 7 Each component shown in the figure can be implemented by hardware, software or a combination thereof. The electronic device 500 may be a physical device, such as a PC, a laptop, a tablet computer, a mobile phone, a wearable device, a home appliance, a robot, an industrial device, a vehicle, etc., or a virtual device, such as a virtual machine, a virtualized container, etc. Moreover, the electronic device 500 is not limited to a single device, but may also be a combination of multiple devices.

[0130] For example, the terminal device mentioned in the embodiment of the present application can be used Figure 7 The structure is implemented in .

[0131] An embodiment of the present application also provides a computer program product, which includes computer program instructions. When these computer program instructions are read and executed by a processor of a computer, the method for constructing a management and control network and / or the device management and control method provided in the embodiment of the present application are executed.

[0132] The present application also provides a computer-readable storage medium on which computer program instructions are stored. When these computer program instructions are read and executed by a computer processor, the method for constructing a control network and / or the device control method provided by the present application are executed. For example, the computer-readable storage medium can be implemented as Figure 7 The memory 520 in the electronic device 500.

[0133] The above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for constructing a management and control network, characterized in that: include: Determine the communication connection relationship between the control entities based on the preset connection rules; wherein each control entity includes at least one terminal device to be controlled, and the control entity corresponds to a node in the topological structure of the control network; Based on the communication connection relationship, a data transmission channel is established between the management and control entities to form the management and control network; wherein the data transmission channel corresponds to an edge between nodes in the topological structure; The control entity in the control network performs equipment control in the following manner: obtaining control information; if the control information is generated by the control entity, sending the control information to an adjacent control entity; if the control information is received by the control entity from a source control entity, sending the control information to an adjacent control entity other than the source control entity; wherein the adjacent control entity refers to a control entity with which a data transmission channel is established.

2. The construction method according to claim 1, characterized in that: The topological structure includes a plurality of basic polygons pieced together, and the nodes in the topological structure are vertices of the basic polygons.

3. The construction method according to claim 2, characterized in that: The basic polygon is a hexagon.

4. The construction method according to claim 1, characterized in that: If the management and control entity includes a plurality of terminal devices, the plurality of terminal devices constitute a secondary network of the management and control network, and a connection rule for constructing the secondary network is the same as a connection rule for constructing the management and control network.

5. The construction method according to any one of claims 1 to 4, characterized in that: The management and control network belongs to the application layer network.

6. A device control method, characterized in that: Applied to the current control entity in the control network, each control entity in the control network includes at least one terminal device to be controlled, the control entity corresponds to a node in the topological structure of the control network, and the data transmission channel established between the control entities corresponds to an edge between the nodes in the topological structure; The method comprises: Obtain control information; If the control information is generated by the current control entity, the control information is sent to the adjacent control entity; if the control information is received by the current control entity from the source control entity, the control information is sent to the adjacent control entity except the source control entity; The adjacent control entity refers to a control entity with which a data transmission channel is established.

7. The device control method according to claim 6, characterized in that: The management and control information includes data and / or policies, and the method further includes: Determine whether the version number of the data and / or policy in the control information is the same as the version number of the local data and / or policy of the current control entity; If the version numbers are different, the data and / or policies in the control information are used to update the local data and / or policies of the current control entity.

8. The device control method according to claim 6, characterized in that: The control information includes tasks, and the method further includes: Execute the tasks in the control information.

9. The device control method according to claim 8, characterized in that: The task in the control information is a task that needs to return a result, and executing the task in the control information includes: Execute the tasks in the control information and obtain execution results; The method further comprises: The execution result is sent to the source control entity.

10. The device control method according to claim 6, characterized in that: The control information includes a remote control request, and obtaining the control information includes: receiving the control information from the source control entity; The method further comprises: Determining whether the current controlled entity is a target controlled entity to be controlled by the remote control request in the control information; If the current controlled entity is the target controlled entity, responding to the remote control request to accept remote control; If the current control entity is not the target control entity, a step of sending the control information to adjacent control entities other than the source control entity is performed.

11. The device control method according to any one of claims 6 to 10, characterized in that: The topological structure includes a plurality of hexagons assembled together, the nodes in the topological structure are the vertices of the hexagons, and the adjacent management and control entities refer to at most three management and control entities with which data transmission channels are established with the current management and control entity.

12. A device for constructing a management and control network, characterized in that: include: A connection relationship determination module, used to determine the communication connection relationship between the control entities based on a preset connection rule; wherein each control entity includes at least one terminal device to be controlled, and the control entity corresponds to a node in the topological structure of the control network; A connection relationship establishing module, used to establish a data transmission channel between the management and control entities based on the communication connection relationship to form the management and control network; wherein the data transmission channel corresponds to an edge between nodes in the topological structure; The control entity in the control network performs equipment control in the following manner: obtaining control information; if the control information is generated by the control entity, sending the control information to an adjacent control entity; if the control information is received by the control entity from a source control entity, sending the control information to an adjacent control entity other than the source control entity; wherein the adjacent control entity refers to a control entity with which a data transmission channel is established.

13. A device control device, characterized in that: Current control entities configured in the control network, each control entity in the control network includes at least one terminal device to be controlled, the control entities correspond to nodes in the topological structure of the control network, and the data transmission channels established between the control entities correspond to edges between nodes in the topological structure; The device comprises: Information acquisition module, used to obtain management and control information; an information forwarding module, configured to send the control information to an adjacent control entity when the control information is generated by the current control entity, and to send the control information to an adjacent control entity other than the source control entity when the control information is received by the current control entity from a source control entity; The adjacent control entity refers to a control entity with which a data transmission channel is established.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are read and executed by a processor, the method according to any one of claims 1 to 11 is executed.

15. An electronic device, characterized in that: The method comprises a memory and a processor, wherein the memory stores computer program instructions, and when the computer program instructions are read and executed by the processor, the method according to any one of claims 1 to 11 is executed.

Images