Networking control method and apparatus, electronic device and storage medium

Abstract

Embodiments of the present application disclose a networking control method and apparatus, an electronic device and a storage medium. The networking control method comprises: a master network device among a plurality of network devices receiving an address allocation request sent by each slave network device among the plurality of network devices, wherein the master network device and the slave network devices are elected on the basis of the role priorities of the plurality of network devices; sending to the slave network devices TIPC address information allocated to the slave network devices; and on the basis of a communication connection established with a cloud server, sending TIPC address information of the master network device and the TIPC address information of the slave network devices to the cloud server, wherein the TIPC address information allows the cloud server to perform configuration management on the master network device and the slave network devices.

Description

Network control method, device, electronic device and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 13, 2023, with application number 202311180996.4 and invention name “A networking control method, device, electronic device and storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a networking control method, device, electronic device, and storage medium. Background Art

[0004] With the widespread adoption of wireless networks, centralized wireless network architectures have become the preferred wireless networking approach due to their ease of implementation, operation, and management. Related technologies employ centralized management methods, such as wireless access controllers (ACs) and cloud-based centralized management, to configure and manage wireless access points (APs), establishing centralized wireless networks.

[0005] Summary of the Invention

[0006] Embodiments of the present application provide a networking control method, device, electronic device, and storage medium.

[0007] In a first aspect, an embodiment of the present application provides a networking control method, including:

[0008] A master network device among a plurality of network devices receives an address allocation request sent by a slave network device among the plurality of network devices, wherein the master network device and the slave network device are selected according to the role priorities of the plurality of network devices;

[0009] The master network device sends the transparent inter-process communication (TIPC) address information allocated to the slave network device to the slave network device; and

[0010] The master network device sends the TIPC address information of the master network device and the TIPC address information of the slave network device to the cloud server based on the communication connection established with the cloud server, wherein the TIPC address information allows the cloud server to configure and manage the master network device and the slave network device.

[0011] In one embodiment, the role priority includes a preset role priority and a resource role priority.

[0012] In one embodiment, the resource role priority is determined based on hardware resource capabilities and / or current software resource information; wherein the hardware resource capabilities include one or more of memory size or device model, and the software resource information includes one or more of memory occupancy or central processing unit CPU occupancy.

[0013] In one embodiment, before the master network device receives the address allocation request sent by the slave network device, the method further includes:

[0014] The master network device is elected based on the preset role priorities and the resource role priorities of the multiple network devices.

[0015] In one embodiment, the selecting the master network device based on the preset role priorities and current software resource information of the multiple network devices includes:

[0016] electing the master network device based on the preset role priorities of the plurality of network devices; and

[0017] When the preset role priorities of the multiple network devices are all the same, the master network device is elected based on the resource role priorities of the multiple network devices.

[0018] In one embodiment, the selecting the master network device based on the preset role priorities of the multiple network devices includes:

[0019] When a first network device of the plurality of network devices is powered on and started, the first network device sends first capability notification information, wherein the first capability notification information includes a first preset role priority and a first resource role priority of the first network device; and

[0020] When the first network device does not receive capability notification information sent by any network device among the multiple network devices within a preset time period, the first network device determines that the first network device is the master network device.

[0021] In one embodiment, the method further comprises:

[0022] When the first network device receives second capability notification information from a second network device among the multiple network devices within the preset time period, comparing the first preset role priority with the second preset role priority of the second network device; and

[0023] When the first preset role priority is lower than the second preset role priority, the first network device no longer sends capability notification information.

[0024] In one embodiment, the method further comprises:

[0025] When the first preset role priority is higher than the preset role priority of the second network device, the capability notification information continues to be sent.

[0026] In one embodiment, when the preset role priorities of the multiple network devices are all the same, electing the master network device based on the resource role priorities of the multiple network devices includes:

[0027] When the first preset role priority is the same as the second preset role priority, comparing the first resource role priority of the first network device with the second resource role priority of the second network device;

[0028] When the first resource role priority is higher than the second resource role priority, the first network device continues to send capability notification information; and

[0029] When the first resource role priority is lower than the second resource role priority, the first network device no longer sends capability advertisement information.

[0030] In one embodiment, multiple network devices of the same type among the multiple network devices correspond to the same preset role priority.

[0031] In one embodiment, the resource role priorities of the same type of network devices among the plurality of network devices are determined according to their respective hardware resource capability information and software resource information.

[0032] In one embodiment, the method further comprises:

[0033] The primary network device receives the local network identity information issued by the cloud server, where the local network identity is used to identify the ad hoc network to which the primary network device belongs;

[0034] The master network device multicasts and sends out intra-domain synchronization information according to a first preset time period, and the intra-domain synchronization information includes the local network identity information and the Internet Protocol IP address information of the cloud server, so as to synchronize the local network identity information and the IP address information of the cloud server with each slave network device.

[0035] In one embodiment, the method further comprises:

[0036] The master network device sends a neighbor request to a first master network device in an adjacent ad hoc network according to a second preset time period;

[0037] The master network device receives the network device information in the adjacent ad hoc network returned by the first master network device.

[0038] In one embodiment, the method further comprises:

[0039] If it is determined that the thin access point AP has received the intra-domain synchronization information, determining the thin AP as a slave network device and instructing the thin AP to connect to the cloud server; and

[0040] A corresponding TIPC address is allocated to the thin AP so that the thin AP joins the ad hoc network to which the main network device belongs.

[0041] In one embodiment, the ad hoc network to which the master network device belongs further includes a backup master network device corresponding to the master network device; and the method further includes:

[0042] The locally stored data is sent to the backup master network device for backup.

[0043] In one embodiment, different types of network devices correspond to different preset role priorities; the role priorities of network devices of the same type are determined based on their respective hardware resource capability information and software resource information.

[0044] In one embodiment, the method further comprises:

[0045] When it is determined that the master network device is offline, the master network device is re-elected according to the role priorities corresponding to the slave network devices.

[0046] In one embodiment, the master network device receives the address allocation request sent by the slave network device among the multiple network devices, specifically including:

[0047] The master network device receives the address allocation request sent by the slave network device through a preset private communication protocol; and

[0048] Sending the TIPC address information allocated to the slave network device to the slave network device specifically includes:

[0049] The TIPC address information allocated to the slave network device is sent to the slave network device through the preset private communication protocol.

[0050] In a second aspect, an embodiment of the present application provides a networking control device, which is applied to a primary network device, including:

[0051] A first receiving unit is configured to receive an address allocation request sent by a slave network device among the multiple network devices, wherein the master network device and the slave network device are selected according to the role priorities of the multiple network devices;

[0052] A first sending unit is configured to send the transparent inter-process communication (TIPC) address information allocated to the slave network device to the slave network device; and

[0053] The second sending unit is used to send the TIPC address information of the master network device and the TIPC address information of the slave network device to the cloud server based on the communication connection established with the cloud server, wherein the TIPC address information allows the cloud server to configure and manage the master network device and the slave network device.

[0054] In one embodiment, the device further comprises:

[0055] A second receiving unit is configured to receive local network identity information issued by the cloud server, where the local network identity is used to identify the ad hoc network to which the primary network device belongs;

[0056] A multicast unit is used to multicast intra-domain synchronization information according to a first preset time period, wherein the intra-domain synchronization information includes the local network identity information and the Internet Protocol IP address information of the cloud server, so as to synchronize the local network identity information and the IP address information of the cloud server with each slave network device.

[0057] In one embodiment, the device further comprises:

[0058] A third sending unit, configured to send a neighbor request to a first master network device in an adjacent ad hoc network according to a second preset time period;

[0059] The third receiving unit is configured to receive the network device information in the adjacent ad hoc network returned by the first master network device in the adjacent ad hoc network.

[0060] In one embodiment, the device further comprises:

[0061] a determining unit, configured to, if it is determined that a thin access point AP has received the intra-domain synchronization information, determine the thin AP as a slave network device and instruct the thin AP to connect to the cloud server; and

[0062] The allocating unit is configured to allocate a corresponding TIPC address to the thin AP so that the thin AP joins the ad hoc network to which the main network device belongs.

[0063] In one embodiment, the ad hoc network to which the master network device belongs further includes a backup master network device corresponding to the master network device; and the apparatus further includes:

[0064] The fourth sending unit is used to send the locally stored data to the backup active network device for backup.

[0065] In one embodiment, different types of network devices correspond to different preset role priorities; the role priorities of network devices of the same type are determined based on their respective hardware resource capability information and software resource information.

[0066] In one embodiment, the device further comprises:

[0067] The election unit is configured to re-elect the master network device according to the role priorities corresponding to the slave network devices if it is determined that the master network device is offline.

[0068] In one embodiment, the first receiving unit is configured to receive the address allocation request sent by the slave network device via a preset private communication protocol;

[0069] The first sending unit is configured to send the TIPC address information allocated to the slave network device to the slave network device through the preset private communication protocol.

[0070] In a third aspect, an embodiment of the present application provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the networking control method described in the present application when executing the program.

[0071] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps in the networking control method described in the present application are implemented.

[0072] In a fifth aspect, an embodiment of the present application provides a computer program product on which a computer program is stored, and when the program is executed by a processor, the steps in the networking control method described in the present application are implemented.

[0073] The networking control method, device, electronic device, and storage medium provided in the embodiments of the present application select a master network device and a slave network device according to the role priority corresponding to each network device. The master network device receives the address allocation request sent by each slave network device and allocates a transparent inter-process communication (TIPC) address to each slave network device. The master network device establishes a communication connection with the cloud server, and sends its own TIPC address information and the TIPC address information of each slave network device to the cloud server, so that the cloud server can configure and manage the master network device and each slave network device. In this way, self-organizing networking is achieved across devices, which is easy to deploy and no longer relies on the AC to perform unified and centralized configuration management of the AP. After the master network device establishes a communication connection with the cloud server, the master network device can send the TIPC address information of the master network device and the TIPC address information of each slave network device to the cloud server. The cloud server can realize unified configuration management of the master network device and each slave network device based on the TIPC address information of the master network device and the TIPC address information of each slave network device, without the need for each network device to actively establish a communication connection with the cloud server respectively. In this way, while reducing the networking cost, the networking reliability and the applicability of the networking method are improved.

[0074] Other features and advantages of the present application will be described in the following description, and in part will become apparent from the description, or will be understood by practicing the present application. The purposes and other advantages of the present application can be realized and obtained by the structures particularly pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0075] The drawings described herein are used to provide further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application.

[0076] FIG1 is a schematic diagram of an application scenario of the networking control method provided in an embodiment of the present application.

[0077] FIG2 is a schematic diagram of the implementation flow of the networking control method provided in an embodiment of the present application.

[0078] FIG3 is a schematic diagram of the structure of a networking control device provided in an embodiment of the present application.

[0079] FIG4 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0080] Embodiments of the present application provide a networking control method, device, electronic device, and storage medium.

[0081] The preferred embodiments of the present application are described below in conjunction with the drawings in the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application and are not used to limit the present application. In addition, the embodiments and features in the embodiments of the present application can be combined with each other if there is no conflict.

[0082] The terms "first," "second," and the like in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this application can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "first," "second," and the like generally distinguish objects of a class and do not limit the number of objects. For example, the first object may be one or more.

[0083] In this document, the term "and / or" simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0084] The terms "at least one" and "at least one of" in the specification and claims of this application refer to any one, any two, or a combination of more than two of the objects included. For example, at least one of a, b, and c can be represented by: "a", "b", "c", "a and b", "a and c", "b and c", and "a, b, and c", where a, b, and c can be single or multiple. Similarly, "at least two" means two or more, and its meaning is similar to "at least one".

[0085] The implementation of the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0086] With the development of wireless networks, the two centralized management methods mentioned above have begun to face challenges in meeting the wireless networking needs of small and medium-sized customers, including high networking costs, poor usability, and low reliability. Furthermore, as customer business scale increases, large-scale wireless LANs are increasingly deployed in scenarios such as campuses and higher education, placing increasingly stringent requirements on the AC's hardware and software architecture. Improving network performance by enhancing hardware capabilities and improving centralized management software performance is costly and has limited applicability.

[0087] Therefore, how to reduce the cost of networking and improve the reliability of networking and the applicability of networking methods is a technical problem that needs to be solved urgently. First, refer to Figure 1, which is a schematic diagram of an application scenario of the networking control method provided in an embodiment of the present application. Network devices in the same virtual local area network (English: Virtual Local Area Network, abbreviated as VLAN) or the same wireless local area network (English: Wireless Local Area Network, abbreviated as WLAN) can perform cross-device self-organizing networking. The application scenario shown in Figure 1 includes a self-organizing network 10 and a cloud server 11. The network devices in the self-organizing network 10 are in the same VLAN or in the same WLAN. The network devices may include but are not limited to one or more of the following devices: gateways, switches, routers, firewalls, ACs, APs, easy gateways (English: E-Gateway, abbreviated as EG) and other devices. Each network device elects a master network device 101 and each slave network device 102 according to their corresponding role priority. The role priority represents the priority of the role election. The role priority of the master network device 101 The role priority of each slave network device 102 is higher than that of each slave network device 102. After the master network device 101 and the slave network device 102 are selected, the master network device 101 generates a TIPC address as its own address. The master network device 101 receives the address allocation request sent by each slave network device 102, allocates a corresponding TIPC address to each slave network device 102, and sends the TIPC address allocated to each slave network device 102 to the corresponding slave network device 102. Then, the master network device 101 and each slave network device 102 can communicate without an IP address through a preset private communication protocol, wherein the preset private communication protocol is an inter-device communication protocol (English: Inter-Device Communication Protocol). The cross-device communication protocol supports cross-device communication between network devices. The message using the cross-device protocol has a specific header, which can prevent irrelevant business perception of self-organizing network messages between different VLANs or WLANs; wherein, the message header of the cross-device communication protocol is used to encapsulate the TIPC message when transmitting business data messages between network devices in the self-organizing network. After receiving the TIPC message encapsulated with the IDCP header (the TIPC message encapsulated with the IDCP header is actually an IDCP message), the receiver can decapsulate the IDCP message and then extract the TIPC message. The structure of the IDCP header can be set according to needs, and the embodiment of the present application does not limit this.Furthermore, after the master network device 101 establishes a communication connection with the cloud server 11, the master network device 101 sends its own TIPC address information and the TIPC address information of each slave network device 102 to the cloud server 11. The cloud server 11 records the TIPC address information of the master network device 101 and the TIPC addresses of each slave network device 102, and centrally performs unified configuration management for the master network device 101 and the slave network devices 102. In the embodiment of the present application, a network device can also be elected as a backup master network device 101' corresponding to the master network device 101. The backup master network device 101' is used to back up the data stored in the master network device 101.

[0088] Based on the above application scenarios, exemplary embodiments of the present application will be described in more detail below with reference to Figures 2 to 4. It should be noted that the above application scenarios are merely provided to facilitate understanding of the spirit and principles of the present application, and the implementation methods of the present application are not limited thereto. On the contrary, the implementation methods of the present application can be applied to any applicable scenario.

[0089] As shown in FIG2 , it is a schematic diagram of the implementation flow of the networking control method provided in an embodiment of the present application. The networking control method may include the following steps.

[0090] S21. The master network device receives an address allocation request sent by the slave network device.

[0091] The master network device and the slave network device are selected based on their respective role priorities. In the embodiment of the present application, the role priority may include a preset role priority and a resource role priority. Different types of network devices correspond to different preset role priorities. The resource role priority of network devices of the same type is determined based on their respective hardware resource capabilities and software resource information.

[0092] During specific implementation, for different types of network devices, the role priorities corresponding to different types of network devices (i.e., preset role priorities) can be pre-set. For example, it can be set as follows: preset role priority of gateway > preset role priority of switch > preset role priority of router > preset role priority of router > preset role priority of firewall > preset role priority of AC > preset role priority of AP > preset role priority of EG. During implementation, it can be set according to needs, and the embodiments of the present application do not limit this. For network devices of the same type, the network device can determine its role priority (i.e., resource role priority) based on its own hardware resource capability information and current software resource information, wherein the hardware resource capability information of the network device can include, but is not limited to, indicators such as memory size and device model, and the software resource information can include, but is not limited to, indicators such as memory occupancy, memory idle rate, CPU occupancy, and CPU idle rate. For example, the resource role priority can be determined by setting different weight ratios for software resources or hardware resource capability information. For example, when the resource role priority of a network device is determined by the CPU idle rate and the memory idle rate, the CPU idle rate can be weighted as 100 and the memory idle rate can be weighted as 10; when the CPU idle rate of network device A is 50 and the memory idle rate is 60, the resource capacity value of network device A = 50*100+60*10=5600; when the CPU idle rate of network device B is 40 and the memory idle rate is 80, the resource capacity value of network device B = 40*100+80*10=4800; the resource capacity value of network device A is greater than the resource capacity value of network device B, so the resource role priority of network device A is higher than the resource role priority of network device B.

[0093] During implementation, after the network device is powered on and started, it can multicast and send out capability announcement information according to the preset private communication protocol, i.e., the cross-device communication protocol, wherein the capability announcement information includes the preset role priority of the network device and the resource role priority determined according to its own hardware resource capability information and current software resource information. When a network device receives capability announcement information sent by any other network device, it first compares its own preset role priority with the preset role priority of the other network devices. If it is determined that its own preset role priority is higher than the preset role priority of other network devices, it continues to send out capability announcement information; if it is determined that its own preset role priority is the same as the preset role priority of other network devices, it continues to compare the resource role priority determined according to its own hardware resource capability information and current software resource information with the resource role priority determined by other network devices according to their own hardware resource capability information and current software resource information. If it is determined that the resource role priority determined according to its own hardware resource capability information and current software resource information is higher than the resource role priority determined by other network devices according to their own hardware resource capability information and current software resource information, it continues to compare the resource role priority determined according to its own hardware resource capability information and current software resource information with the resource role priority determined by other network devices according to their own hardware resource capability information and current software resource information. If the priority of the resource role determined based on its own hardware resource capability information and current software resource information is lower than the priority of the resource role determined by other network devices based on their own hardware resource capability information and current software resource information, the network device will remain silent and will no longer send capability notification information. If the priority of the resource role determined based on its own hardware resource capability information and current software resource information is the same as the priority of the resource role determined by other network devices based on their own hardware resource capability information and current software resource information, then either the network device or the other network device will continue to send capability notification information or both will continue to send capability notification information. If the network device determines that its own preset role priority is lower than the preset role priority of other network devices, the network device will remain silent and will no longer send capability notification information. In this way, when the network device itself continues to send capability notification information and does not receive capability notification information from any other network device within the preset time period, it can be determined that the role priority of the network device is the highest, and the network device can be elected as the master network device, and the other network devices can be elected as slave network devices.

[0094] In one embodiment, after the master network device and the slave network device are elected, the master network device may further designate a slave network device among the slave network devices as a backup master network device. For example, it may be possible but not limited to designating a slave network device with the highest role priority as a backup master network device. The backup master network device is used to back up the data stored in the master network device. In this way, when the master network device abnormally goes offline, the backup master network device can automatically switch to the master network device, thereby ensuring uninterrupted business.

[0095] In one implementation, the primary network device may also be specified by the user, which is not limited in this embodiment of the present application.

[0096] Furthermore, the master network device generates a TIPC address as its own communication address, and a timed keep-alive mechanism is used between the master network device and each slave network device to monitor in real time whether there is any abnormality in the communication link between the master network device and each slave network device.

[0097] The master network device and the slave network device in the same VLAN or WLAN can exchange data through a preset private communication protocol, that is, a cross-device communication protocol. The slave network device sends an address allocation request to the master network device through the preset private communication protocol, that is, a cross-device communication protocol, to request the master network device to allocate a TIPC address for it as a communication address. In this way, communication without an IP address can be achieved between the master network device and the slave network device.

[0098] S22. The master network device sends the TIPC address information allocated to the slave network device to the slave network device.

[0099] In specific implementation, for each slave network device, when the master network device receives the address allocation request sent by the slave network device, it allocates a TIPC address to the slave network device and sends the TIPC address to the slave network device via a preset private communication protocol, namely, a cross-device communication protocol.

[0100] In an embodiment of the present application, when a network device is started online and determines that its role is a slave network device, it can issue an address allocation request, or the network device can send an address allocation request regularly according to a predetermined period. This embodiment of the present application does not limit this.

[0101] S23. The master network device sends its own TIPC address information and the TIPC address information of each slave network device to the cloud server based on the communication connection established with the cloud server, so that the cloud server can configure and manage the master network device and each slave network device.

[0102] During specific implementation, the master network device can, but is not limited to, establish a communication connection with the cloud server through the Hypertext Transfer Protocol (English: Hypertext Transfer Protocol, abbreviated as HTTP), and send the TIPC address information of the master network device and the TIPC address information of each slave network device to the cloud server. It can also establish a communication connection with the cloud server by scanning the QR code of the master network device for communication connection, and send the TIPC address information of the master network device and the TIPC address information of each slave network device to the cloud server. The embodiments of the present application are not limited to this.

[0103] After receiving the TIPC address information of the master network device and each slave network device from the master network device, the cloud server sets a local network identity document (LNID) for the master network device. The LNID uniquely identifies the ad hoc network to which the master network device belongs and records the correspondence between the LNID and the TIPC addresses of the master network device and the slave network devices. The cloud server then sends the LNID information to the master network device. The cloud server can set different LNIDs for different master network devices.

[0104] The master network device receives the local network identity information sent by the cloud server, and multicasts and sends domain synchronization information to multiple slave network devices through the cross-device communication protocol according to the first preset time period. The domain synchronization information includes the local network identity information and the IP address information of the cloud server to synchronize the local network identity information and the IP address information of the cloud server with each slave network device. After each slave network device receives the domain synchronization information, it stores the local network identity information and the IP address information of the cloud server locally. The first preset time period can be set according to needs, and the embodiments of the present application are not limited to this. After each slave network device receives the local network identity information of the self-organizing network to which it belongs and the IP address information of the cloud server, it can be networked with other slave network devices and the master network device in the current VLAN or WLAN according to the local network identity information, and can communicate and connect with the cloud server according to the IP address information of the cloud server. Then, the cloud server performs centralized and unified configuration management of the master network device and each slave network device, thereby realizing communication connection with the cloud server through a master network device, and connecting all network devices in the entire self-organizing network with the cloud server. The cloud server performs centralized and unified configuration management of all network devices in the entire self-organizing network.

[0105] Network devices in the same VLAN or WLAN can exchange data in a multicast manner through a cross-device communication protocol. A VLAN or WLAN can include multiple self-organizing networks. The main network device can send a neighbor request to the main network device in the adjacent self-organizing network according to a second preset time period to request information about each network device in the adjacent self-organizing network, thereby perceiving other self-organizing networks in the same VLAN or WLAN. The second preset time period can be set according to needs, and the embodiments of the present application are not limited to this.

[0106] During specific implementation, the master network device multicasts neighbor request information through a cross-device communication protocol. If the master network device in the adjacent self-organizing network receives the neighbor request information, the locally stored information of each network device in the adjacent self-organizing network is returned to the master network device, namely, the master network device information and the slave network device information. The network device information in the adjacent self-organizing network may include, but is not limited to, at least one or more of the following information: TIPC address information of all network devices in the adjacent self-organizing network, physical address (English: Media Access Control Address, abbreviated as MAC), role (i.e., master network device or slave network device), serial number (English: Serial Number, abbreviated as SN), device model, software version and other information. The embodiments of the present application do not limit this.

[0107] After receiving the information of each network device in the adjacent ad hoc network sent by the master network device in the adjacent ad hoc network, the master network device may also share the information of all network devices in the ad hoc network to which it belongs with the master network device in the adjacent ad hoc network.

[0108] The same VLAN or WLAN may also include thin APs that are centrally configured and managed by the hard AC using the Control And Provisioning of Wireless Access Points Protocol (CAPWAP) tunnel. When the main network device multicasts and sends out intra-domain synchronization information, if it is determined that the thin AP has received the intra-domain synchronization information, the thin AP can be identified as a slave network device, and the thin AP can be instructed to connect to the cloud server, and the corresponding TIPC address can be assigned to the thin AP so that the thin AP joins the self-organizing network to which the main network device belongs. The main network device sends the TIPC address of the newly added AP to the cloud server, thereby switching the thin AP to a cloud AP for configuration management by the cloud server.

[0109] In one embodiment, if it is determined that the master network device is offline, the master network device may be re-elected based on the role priorities corresponding to the slave network devices.

[0110] In specific implementation, if it is determined that the keep-alive timeout has occurred for all slave network devices in an ad hoc network with the master network device, it can be determined that the master network device has been abnormally disconnected or shut down and disconnected, then all slave network devices can re-elect the master network device. The election method has been described in detail before and will not be repeated here.

[0111] In one embodiment, if it is determined that the master network device is offline, the backup master network device may also switch to the master network device and designate a slave network device with a high role priority from all slave network devices as the new backup master network device.

[0112] After the ad hoc network is established, data packets can be transmitted between network devices in the ad hoc network. The following describes the data transmission process between different network devices.

[0113] The first network device periodically sends a detection message, which is used to discover other network devices. The detection message is an IDCP message, and the detection message carries the port information and MAC address information of the first network device.

[0114] Among them, each network device is pre-configured with a message receiving module to intercept IDCP messages and send them to a central processing unit (CPU) for processing. The port information of the first network device may include, but is not limited to, at least one of the following information: a switch port identity identifier (Switch Identity Document, abbreviated as Switch ID) of the first network device, a slot number (Slot Identity Document, abbreviated as Slot ID, which is a wired port number), and a sub-slot number (Sub-Slot Identity Document, abbreviated as Sub-Slot ID).

[0115] If the second network device receives the detection message sent by the first network device, it returns a response message to the first network device, and the response message carries the port information and MAC address information of the second network device.

[0116] The response message is an IDCP message, and the port information of the second network device may include, but is not limited to, at least one of the following information: Switch ID, Slot ID, and Sub-Slot ID of the second network device.

[0117] In specific implementation, the second network device receives the detection message sent by the first network, parses the port information and MAC address information of the first network device, and stores the correspondence between the port information and MAC address information of the first network device in the database for subsequent table lookup when forwarding business messages.

[0118] After the first network device receives the response message returned by the second network device, it parses the port information and MAC address information of the second network message from the response message, and stores the correspondence between the port information and MAC address information of the second network device in the database for subsequent table lookup when forwarding business messages.

[0119] In this way, the first network device and the second network device can share their port information and MAC address information.

[0120] When a service message is forwarded between a first network device and a second network device through the TIPC protocol, the sender (assuming it is the first network device) performs IDCP encapsulation on the service message to be forwarded at the forwarding adaptation layer, that is, encapsulates the TIPC message with an IDCP protocol header, and then forwards the IDCP-encapsulated TIPC message to the receiver (assuming it is the second network device).

[0121] When the second network device receives the IDCP-encapsulated TIPC message sent by the first network device, it first decapsulates the IDCP at the forwarding adaptation layer to obtain the TIPC message; then it parses the TIPC message, searches for the target port information corresponding to the target MAC address from the stored correspondence between network devices and port information, and forwards the TIPC message to the network device corresponding to the target port.

[0122] The networking control method, device, electronic device and storage medium provided in the embodiment of the present application select a master network device and a slave network device according to the role priority corresponding to each network device, the master network device receives the address allocation request sent by each slave network device, allocates a TIPC address to each slave network device, and sends the TIPC address allocated to each slave network device. The master network device establishes a communication connection with the cloud server, and sends its own TIPC address information and the TIPC address information of each slave network device to the cloud server, so that the cloud server can configure and manage the master network device and each slave network device, thereby realizing cross-device communication. It can perform self-organizing networking, is easy to deploy, and no longer relies on AC to perform unified and centralized configuration management of APs. After the master network device establishes a communication connection with the cloud server, the master network device can send the TIPC address information of the master network device and the TIPC address information of each slave network device to the cloud server. The cloud server can realize unified configuration management of the master network device and each slave network device based on the TIPC address information of the master network device and the TIPC address information of each slave network device, without the need for each network device to actively establish a communication connection with the cloud server. Therefore, while reducing the networking cost, it improves the networking reliability and the applicability of the networking method.

[0123] Based on the same inventive concept, an embodiment of the present application also provides a networking control device. Since the principle of solving the problem by the above-mentioned networking control device is similar to that of the above-mentioned networking control method, the implementation of the above-mentioned device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0124] As shown in FIG3 , which is a schematic diagram of the structure of a networking control device provided in an embodiment of the present application, the networking control device, applied to a primary network device, may include:

[0125] A first receiving unit 31 is configured to receive an address allocation request sent by a slave network device, wherein the master network device and the slave network device are selected according to their corresponding role priorities;

[0126] A first sending unit 32 is configured to send the transparent inter-process communication (TIPC) address information allocated to the slave network device to the slave network device;

[0127] The second sending unit 33 is configured to send its own TIPC address information and the TIPC address information of each slave network device to the cloud server based on the communication connection established with the cloud server, so that the cloud server can perform configuration management on the master network device and the slave network devices.

[0128] In one embodiment, the device further comprises:

[0129] A second receiving unit is configured to receive local network identity information issued by the cloud server, where the local network identity is used to identify the ad hoc network to which the primary network device belongs;

[0130] A multicast unit is used to multicast and send out domain synchronization information according to a first preset time period, wherein the domain synchronization information includes the local network identity information and the Internet Protocol IP address information of the cloud server, so as to synchronize the local network identity information and the IP address information of the cloud server with each slave network device.

[0131] In one embodiment, the device further comprises:

[0132] A third sending unit, configured to send a neighbor request to a master network device in an adjacent ad hoc network according to a second preset time period;

[0133] The third receiving unit is configured to receive information about each network device in the adjacent ad hoc network returned by a master network device in the adjacent ad hoc network.

[0134] In one embodiment, the device further comprises:

[0135] a determining unit, configured to, if it is determined that a thin access point AP has received the intra-domain synchronization information, determine the thin AP as a slave network device and instruct the thin AP to connect to the cloud server;

[0136] The allocating unit is configured to allocate a corresponding TIPC address to the thin AP so that the thin AP joins the ad hoc network to which the main network device belongs.

[0137] In one embodiment, the ad hoc network to which the master network device belongs further includes a backup master network device corresponding to the master network device; and the apparatus further includes:

[0138] The fourth sending unit is used to send the locally stored data to the backup active network device for backup.

[0139] In one implementation, the role priority of the master network device is higher than the role priority of each slave network device.

[0140] In one embodiment, the device further comprises:

[0141] The election unit is configured to re-elect the master network device according to the role priorities corresponding to the slave network devices if it is determined that the master network device is offline.

[0142] In one embodiment, the first receiving unit 32 is specifically configured to receive the address allocation request sent by the slave network device via a preset private communication protocol;

[0143] The first sending unit 32 is specifically configured to send the TIPC address information allocated to the slave network device to the slave network device through the preset private communication protocol.

[0144] Based on the same technical concept, an embodiment of the present application further provides an electronic device 400. Referring to FIG. 4 , the electronic device 400 is configured to implement the networking control method described in the above method embodiments. The electronic device 400 of this embodiment may include a memory 401, a processor 402, and a computer program stored in the memory and executable on the processor, such as a networking program. When the processor executes the computer program, the steps of each of the above networking control method embodiments are implemented.

[0145] The specific connection medium between the memory 401 and the processor 402 is not limited in the embodiments of the present application. In Figure 4, the memory 401 and the processor 402 are connected via a bus 403. Bus 403 is represented by a bold line in Figure 4. The connection methods between other components are merely illustrative and not limiting. The bus 403 can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 4 only uses a single bold line, but this does not mean that there is only one bus or only one type of bus.

[0146] Memory 401 may be a volatile memory, such as random-access memory (RAM); a non-volatile memory, such as read-only memory, flash memory, a hard disk drive (HDD), or a solid-state drive (SSD); or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. Memory 401 may be a combination of the above memories.

[0147] Processor 402 is used to implement the networking control method provided in the embodiment of the present application.

[0148] An embodiment of the present application also provides a computer-readable storage medium that stores computer-executable instructions required to execute the above-mentioned processor, which includes a program required to execute the above-mentioned processor.

[0149] In some possible implementations, various aspects of the networking control method provided in the present application can also be implemented in the form of a program product, which includes program code. When the program product is run on an electronic device, the program code is used to enable the electronic device to execute the steps of the networking control method according to various exemplary implementations of the present application described above in this specification.

[0150] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, devices, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0151] The present application is described with reference to the flow chart and / or block diagram of the method, equipment (device) and computer program product according to the embodiment of the present application. It should be understood that each flow process and / or box in the flow chart and / or block diagram and the combination of the flow process and / or box in the flow chart and / or block diagram can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processing machine or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for realizing the function specified in one flow chart flow or multiple flows and / or one box or multiple boxes of the block diagram.

[0152] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0153] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0154] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present application.

[0155] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A networking control method, comprising: A master network device among a plurality of network devices receives an address allocation request sent by a slave network device among the plurality of network devices, wherein the master network device and the slave network device are selected according to the role priorities of the plurality of network devices; The master network device sends the transparent inter-process communication TIPC address information allocated to the slave network device to the slave network device; and The master network device sends the TIPC address information of the master network device and the TIPC address information of the slave network device to the cloud server based on the communication connection established with the cloud server, wherein the TIPC address information allows the cloud server to perform configuration management on the master network device and the slave network device.

2. The method of claim 1, wherein: The role priority includes a preset role priority and a resource role priority.

3. The method of claim 2, wherein: The resource role priority is determined based on hardware resource capabilities and / or current software resource information; wherein the hardware resource capabilities include one or more of memory size or device model, and the software resource information includes one or more of memory occupancy or central processing unit CPU occupancy.

4. The method according to any one of claims 1 to 3, wherein: Before the master network device receives the address allocation request sent by the slave network device, the method further includes: The master network device is elected based on the preset role priorities and the resource role priorities of the multiple network devices.

5. The method of claim 4, wherein: The selecting the master network device based on the preset role priorities and current software resource information of the multiple network devices includes: electing the master network device based on the preset role priorities of the plurality of network devices; and When the preset role priorities of the multiple network devices are all the same, the master network device is elected based on the resource role priorities of the multiple network devices.

6. The method of claim 5, wherein: The step of electing the master network device based on the preset role priorities of the multiple network devices includes: When a first network device of the plurality of network devices is powered on and started, the first network device sends a first capability notification message, wherein the first capability notification message includes a first preset role priority and a first resource role priority of the first network device; and When the first network device does not receive capability notification information sent by any network device among the multiple network devices within a preset time period, the first network device determines that the first network device is a master network device.

7. The method of claim 4, wherein: The method further comprises: When the first network device receives the second capability notification information sent by the second network device among the multiple network devices within the preset time period, the first preset role priority is compared with the second preset role priority of the second network device; and When the first preset role priority is lower than the second preset role priority, the first network device no longer sends capability notification information.

8. The method of claim 7, wherein: The method further comprises: When the first preset role priority is higher than the preset role priority of the second network device, the capability notification information continues to be sent.

9. The method of claim 7, wherein: When the preset role priorities of the multiple network devices are all the same, electing the master network device based on the resource role priorities of the multiple network devices includes: When the first preset role priority is the same as the second preset role priority, comparing the first resource role priority of the first network device with the second resource role priority of the second network device; When the first resource role priority is higher than the second resource role priority, the first network device continues to send capability notification information; and When the first resource role priority is lower than the second resource role priority, the first network device no longer sends capability notification information.

10. The method according to any one of claims 1 to 9, wherein: Multiple network devices of the same type among the multiple network devices correspond to the same preset role priority.

11. The method according to any one of claims 1 to 10, wherein: The resource role priorities of the multiple network devices of the same type among the multiple network devices are determined according to their respective hardware resource capability information and software resource information.

12. The method according to any one of claims 1 to 11, wherein: The method further comprises: The primary network device receives the local network identity information sent by the cloud server, wherein the local network identity is used to identify the ad hoc network to which the primary network device belongs; and The master network device multicasts intra-domain synchronization information according to a first preset time period, wherein the intra-domain synchronization information includes the local network identity information and the Internet Protocol IP address information of the cloud server.

13. The method according to any one of claims 1 to 12, wherein: The method further comprises: The master network device sends a neighbor request to a first master network device in an adjacent ad hoc network according to a second preset time period; and The master network device receives the network device information in the adjacent ad hoc network returned by the first master network device.

14. The method according to claim 12 or 13, wherein: The method further comprises: When it is determined that the thin access point AP receives the intra-domain synchronization information, the thin AP is determined as a slave network device, and the thin AP is instructed to connect to the cloud server; and A corresponding TIPC address is allocated to the thin AP so that the thin AP joins the ad hoc network to which the main network device belongs.

15. The method according to any one of claims 1 to 14, wherein: The ad hoc network to which the master network device belongs also includes a backup master network device corresponding to the master network device, and the method further includes: The master network device sends the locally stored data to the backup master network device for backup.

16. The method according to any one of claims 1 to 15, wherein: The master network device receives the address allocation request sent by the slave network device among the multiple network devices, comprising: The master network device receives the address allocation request sent by the slave network device through a preset private communication protocol.

17. The method of claim 16, wherein: The step of sending the TIPC address information allocated to the slave network device to the slave network device includes: The TIPC address information allocated to the slave network device is sent to the slave network device through the preset private communication protocol.

18. A networking control device, applied to a master network device among a plurality of network devices, comprising: A first receiving unit is configured to receive an address allocation request sent by a slave network device among the multiple network devices, wherein the master network device and the slave network device are selected according to the role priorities of the multiple network devices; A first sending unit, configured to send the transparent inter-process communication TIPC address information allocated to the slave network device to the slave network device; and The second sending unit is used to send the TIPC address information of the master network device and the TIPC address information of the slave network device to the cloud server based on the communication connection established with the cloud server, wherein the TIPC address information allows the cloud server to configure and manage the master network device and the slave network device.

19. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the networking control method according to any one of claims 1 to 17 is implemented.

20. A computer-readable storage medium having a computer program stored thereon, wherein: When the program is executed by a processor, the steps in the networking control method according to any one of claims 1 to 17 are implemented.

Images