CN115442870A

CN115442870A - MESH networking method and system

Info

Publication number: CN115442870A
Application number: CN202211384188.5A
Authority: CN
Inventors: 石冬雪
Original assignee: Hangzhou Ruisike Technology Co ltd
Current assignee: Hangzhou Ruisike Technology Co ltd
Priority date: 2022-11-07
Filing date: 2022-11-07
Publication date: 2022-12-06

Abstract

The application relates to a MESH networking method and a MESH networking system, wherein the MESH networking method comprises the following steps: under the condition that equipment in each MESH network receives a joining request sent by equipment outside the MESH network, reporting request information to a cloud platform for decision making of the cloud platform; the cloud platform determines an access point according to a received request information comprehensive decision reported by the devices in the MESH networks, and informs the access point to access the devices outside the MESH networks; through the method and the device, the problem that the most reasonable upper-level equipment is not accessed when the MESH equipment is networked, and inconvenience is brought to MESH node management is solved, the access of the MESH equipment is reasonable upper-level equipment every time the MESH equipment is networked, and convenience is brought to MESH node management.

Description

MESH networking method and system

Technical Field

The present application relates to the field of wireless MESH discovery and routing technology, and in particular, to a MESH networking method and system.

Background

The wireless MESH network is a new type of wireless local area network. Different from the conventional WLAN, the Access Points (APs) in the wireless MESH network may be interconnected in a wireless connection manner, and a multi-hop wireless link may be established between the APs. In a wireless MESH network, each node of any wireless device can simultaneously act as a MESH node and a wireless router, each node in the network can send and receive signals, and each node can directly communicate with one or more peer nodes. Wireless MESH networks remove the wiring requirements between nodes but still have the redundancy mechanisms and rerouting functionality provided by distributed networks.

In the wireless MESH network, if a new device is added, only power supply is needed to be connected, and the wireless MESH network can automatically perform self configuration and determine the optimal multiple transmission paths. When the device is added or moved, the network can automatically discover the topology change and automatically adjust the communication route to acquire the most effective transmission path. Thus, MESH has the following advantages: 1. automatic seamless roaming is realized, and the line is not dropped during route crossing. The weak signal is automatically removed, and the strong router signal is automatically connected. 2. The wireless configuration information can be automatically synchronized, a main router (a mother router) is modified, and the sub-router can automatically synchronize wifi and other parameter configuration information. 3. The topology is self-adaptive, and the connection mode is divided into: wired connection, wireless connection, wired and wireless hybrid connection. 4. The installation is relatively simple, and the deployment is very flexible, especially wireless backhaul mode, if want to increase coverage area. The problem can be solved by adding a plurality of devices.

In the related art, in order to configure the MESH, the following steps are required: step 1: configuring a wireless router into a main route, accessing the Internet (INTERNET), establishing connection with a cloud platform, and step 2: if the MESH nodes and the wireless router are expected to carry out MESH networking, a WPS key of the wireless router is pressed, within the time limit of 2 minutes, the WPS key of the MESH node is pressed, an indicator lamp flashes to enter a networking mode, the indicator lamp turns green to indicate that the connection is successful, otherwise, the connection is failed, if the MESH nodes and another MESH node are expected to be networked, the WPS key of the MESH node can be pressed, and the WPS key of the another MESH node is pressed within the time limit of 2 minutes.

This manual key method requires the user to manually select the upper level and press the corresponding upper WPS key, but obviously, the user only knows to join a wireless MESH device (for example, add a MESH node), but it is not clear which upper level the wireless MESH device should be combined with. Therefore, the last access superior node of the wireless MESH device is often not the most reasonable, which brings great inconvenience to the management of the MESH node.

In the related art, an effective solution is not provided for the problem that the access of the MESH device is not the most reasonable upper-level device when networking, which brings inconvenience to MESH node management.

Disclosure of Invention

The embodiment of the application provides a MESH networking method and a MESH networking system, which are used for at least solving the problem that access of MESH equipment in the related technology is not the most reasonable upper-level equipment, and inconvenience is brought to MESH node management.

In a first aspect, an embodiment of the present application provides a MESH networking method, where the method includes:

the method comprises the steps that under the condition that equipment in each MESH network receives a joining request sent by equipment outside the MESH network, request information is reported to a cloud platform for decision-making of the cloud platform;

the cloud platform determines an access point according to a received request information comprehensive decision reported by the devices in the MESH networks, and informs the access point of accessing the devices outside the MESH networks.

In some embodiments, before the cloud platform determines the access point, the method further comprises: the cloud platform receives a decision starting instruction issued by the user side, and executes a decision in response to the decision starting instruction to determine the access point.

In some embodiments, the cloud platform determines the access point according to a received request information comprehensive decision reported by the devices in the multiple MESH networks, and the process includes:

traversing each state into effective data in the received request information by the cloud platform, and comprehensively deciding to determine an access point; and when the equipment outside the MESH network finishes networking or the networking is overtime, the cloud platform sets the state of the corresponding data to be invalid.

the cloud platform determines the node topological relation and the load level of the equipment according to the wireless access point of the equipment in the MESH network in the request information, and determines the optimal access point according to the preset priority sequence by combining the signal strength of the equipment in the request information, which receives the equipment outside the MESH network.

In some embodiments, the accessing, by the access point, a device outside the MESH network includes:

the access point opens a service set identifier and waits for the equipment outside the MESH network to join;

the access point detects whether equipment outside the MESH network is accessed within a preset time period, and reports an access result to the cloud platform; and after receiving the access result, the cloud platform sends the access result to the user side.

In some of these embodiments, the method further comprises:

after the equipment to be added into the MESH networking is started, the equipment sends the adding request in a broadcasting mode, or under the condition that the access point is disconnected, the equipment to be added into the MESH networking resends the adding request so that the cloud platform can redetermine the access point according to the received request information.

In a second aspect, an embodiment of the present application provides a MESH networking system, where the system includes: the system comprises a cloud platform, equipment in the MESH network and equipment outside the network to be added into the MESH network;

and the cloud platform determines an access point according to a received request information comprehensive decision reported by the devices in the MESH networks, and informs the access point of accessing the devices outside the MESH networks.

and the cloud platform determines the node topological relation and the load level of the equipment according to the wireless access points of the equipment in the MESH network in the request information, and determines the optimal access point according to the preset priority order by combining the signal strength of the equipment in the request information, which receives the equipment outside the MESH network.

In a third aspect, an embodiment of the present application provides an electronic apparatus, which includes a memory and a processor, where the memory stores a computer program, and the processor is configured to run the computer program to execute the MESH networking method.

In a fourth aspect, an embodiment of the present application provides a storage medium, where a computer program is stored in the storage medium, where the computer program is configured to execute the MESH networking method when running.

Compared with the prior art, the MESH equipment is not the most reasonable upper-level equipment when networking, and the problem of inconvenience for MESH node management is solved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a schematic application environment diagram of a MESH networking method according to an embodiment of the present application;

fig. 2 is a schematic diagram of a MESH networking method according to a first embodiment of the present application;

fig. 3 is a diagram illustrating a MESH networking method according to a second embodiment of the present application;

fig. 4 is a schematic diagram of an interface of an APP-initiated MESH networking according to a third embodiment of the present application;

fig. 5 is a schematic diagram of an interface of an APP polling cloud platform processing result according to a fourth embodiment of the present application;

fig. 6 is an internal structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described and illustrated below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments provided in the present application without any inventive step are within the scope of protection of the present application.

It is obvious that the drawings in the following description are only examples or embodiments of the present application, and that it is also possible for a person skilled in the art to apply the present application to other similar contexts on the basis of these drawings without inventive effort. Moreover, it should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another.

Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the specification. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is to be expressly and implicitly understood by one of ordinary skill in the art that the embodiments described herein may be combined with other embodiments without conflict.

Unless defined otherwise, technical or scientific terms referred to herein shall have the ordinary meaning as understood by those of ordinary skill in the art to which this application belongs. The use of the terms "a" and "an" and "the" and similar referents in the context of describing the invention (including a single reference) are to be construed in a non-limiting sense as indicating either the singular or the plural. The present application is directed to the use of the terms "including," "comprising," "having," and any variations thereof, which are intended to cover non-exclusive inclusions; for example, a process, method, system, article, or apparatus that comprises a list of steps or modules (elements) is not limited to the listed steps or elements, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Reference to "connected," "coupled," and the like in this application is not intended to be limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The term "plurality" as used herein means two or more. "and/or" describes an association relationship of associated objects, meaning that three relationships may exist, for example, "A and/or B" may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. Reference herein to the terms "first," "second," "third," and the like, are merely to distinguish similar objects and do not denote a particular ordering for the objects.

Fig. 1 is a schematic view of an application environment of the MESH networking method according to the embodiment of the present application, and as shown in fig. 1, in a wireless MESH network, a wireless router 10 is uplinked in a wired manner, the wireless router 10 and a cloud platform 20 establish connection through the internet, the wireless router 10 and a MESH node 1 30 establish connection through a wireless network, and an internet access terminal 1 60 is connected to the MESH node 1. When a new MESH device is to join the MESH network, the device to join the MESH network sends out a join REQUEST (PROBE REQUEST) in a broadcasting mode after being started, and the REQUEST has a self-defined MESH REQUEST characteristic so as to be different from the detection of a general wireless terminal.

The networking process is described in detail below, where MESH node 1 has completed the wireless MESH network with wireless router 10, and MESH node 2 is the new wireless MESH node to join as described in the present invention. For convenience of description, the MAC addresses of the wireless router 10, the MESH node 1, and the MESH node 2 are respectively identified as follows, and where the MAC addresses appear in the data table, they can be understood as correspondingly numbered devices instead. Similarly, hereinafter, an Access Point (AP) and a wireless router are used in the same meaning, and in order to facilitate understanding of those skilled in the art in different situations, the AP is referred to as the wireless router in some situations and the AP in some situations.

Fig. 2 is a schematic diagram of a MESH networking method according to a first embodiment of the present application, and as shown in fig. 2, the flow includes the following steps:

step S201, under the condition that equipment in each MESH network receives a joining request sent by equipment outside the MESH network, reporting request information to a cloud platform for decision of the cloud platform;

for example, when a superior neighbor of the same brand receives a join request of a device, the superior neighbor does not directly reply to the request (PROBE RESPONSE), but reports the request to the WIFI cloud platform for the cloud platform to make a comprehensive decision;

step S202, the cloud platform determines an access point according to the received request information comprehensive decision reported by the devices in the MESH networks, and informs the access point to access the devices outside the MESH networks;

for example, the cloud platform calculates the collected information sent by a plurality of neighbors, determines an optimal access point, and informs the optimal access point to take charge of access, after receiving an instruction of accessing the cloud platform to the MESH new node, the optimal access point starts a dedicated Service Set Identifier (SSID for short), and waits for the new node to be added; the new node completes the MESH access within the limited time, successfully establishes the MESH link and reports the cloud platform result; and the cloud platform informs the APP MESH networking result, and the APP popup window prompts the MESH networking result.

Through the above steps S201 to S202, compared to the problem that the access of the MESH device is not the most reasonable upper device when networking is performed in the related art, which brings inconvenience to the MESH node management, in the embodiment of the present application, the device in each MESH network reports the request information to the cloud platform when receiving the join request sent by the device outside the MESH network, and the cloud platform makes a comprehensive decision to determine the best access point, and in an ideal case where the conditions are met, through the method adopted by the present invention, the MESH node 2 40 automatically selects the wireless router 10 as the upper node to join in the wireless MESH network. The method simplifies the MESH configuration process, the user does not need to care which upper-level router the newly added wireless MESH equipment should form a pair with, all the wireless MESH equipment is decided by the cloud platform, the decision importance is more obvious in a large-scale network, and the problem that the access of the MESH equipment is not the most reasonable upper-level equipment when the MESH equipment is networked, and the inconvenience is brought to the MESH node management is solved.

It should be noted that the core of the technical scheme of the invention lies in that the device in the MESH network reports the request information to the cloud platform, the cloud platform comprehensively decides to determine the best access point, replaces the access point manually selected by the user in the related technology, and performs the key connection mode on the two devices within the time limit, compared with the user who does not know that the wireless MESH device is reasonably combined with which higher level, the decision of the cloud platform is established on the basis of the request information reported by multiple devices in the MESH network, so that the access of the MESH device is more reasonable higher level device every time of networking, and the MESH node management is facilitated; the content included in the request message may be all common parameters used in the art to help determine a reasonable access point for the new MESH node, which is not limited in this application. For example, the request information may include a MAC address of the new MESH node, a wireless access point of the device in the MESH network, data generation time, and the like, and the cloud platform determines the node topology relationship and the load level of the device according to the wireless access point of the device in the MESH network in the request information, and determines the optimal access point of the new MESH node according to a preset priority ranking. Alternatively, in some other embodiments, the request message may include information such as signal strength of the device receiving the message from the outside of the MESH network, so as to determine the best access point of the new MESH node according to the rank order of the request signal strength.

In some embodiments, fig. 3 is a schematic diagram of a MESH networking method according to a second embodiment of the present application, and as shown in fig. 3, before a cloud platform determines an access point, the process includes the following steps: step S301, the cloud platform receives a decision starting instruction issued by a user terminal, and executes a decision in response to the decision starting instruction to determine an access point; for example, a user triggers a MESH networking of a new node on an APP by one key to trigger a decision start of a cloud platform, and the cloud platform executes the decision after receiving a decision start instruction to determine an access point. Through the step S301, the user may flexibly control the time for the cloud platform to start the decision through tools such as an application program, and certainly, in other embodiments, the time for the cloud platform to start the decision may also be controlled through a manner of presetting the time for collecting the cloud platform information, and the like.

The implementation method of the patent is described in detail as follows:

1. for adding wireless MESH devices.

The wireless MESH adding device is initiated by an APP, but before the initiation, a new MESH node to be added is powered on, and relevant detection broadcast is sent out and collected by surrounding neighbors and summarized to the cloud platform. The method of constructing this premise will be further explained in the following section on data acquisition. The mode of initiating MESH networking by the APP may be that the APP provides a UI interface, and in the interface, MESH nodes that are already online currently are listed. Fig. 4 is a schematic diagram of an interface of an APP-initiated MESH networking according to a third embodiment of the present application, and as shown in fig. 4, a wireless router and a MESH node 1 are already online at present, and a MESH node 2 is to be added. In the interface, the bottom is provided with an operation button for a user to initiate an adding operation by one key. If the online device list is empty, this button will be grayed out and un-clickable. When the user clicks the bottom "+ add wireless MESH device" button, the add flow of the wireless MESH device is initiated. The flow performed by each network element after this button click is described in detail below. Including APP, cloud platform, online MESH node, following first explains from the APP angle after the button clicks, APP's workflow.

2. The APP initiates a wireless MESH equipment adding process.

With the click of the "+ add wireless MESH device" button by the user, the APP executes the process as follows: step 1, the APP communicates with a cloud platform, and requests to control the online equipment from the cloud end to complete the service of adding the wireless MESH equipment. Step 2, the APP polls the cloud platform processing result within the timeout period, fig. 5 is a schematic diagram of an interface of the APP polls the cloud platform processing result according to the fourth embodiment of the present application, as shown in fig. 5, in this process, an APP popup displays an adding process of a currently-proceeding wireless MESH device in an animation manner, and displays "adding a wireless MESH device, please wait" or a similar prompt. And 3, if the APP obtains a networking success result within the overtime time, displaying a networking success message on an APP interface, and otherwise, prompting a networking failure message.

Further, in step 1, the APP and the cloud platform are kept in a connection state, the APP first generates a service number for the service, and sends the following command to the cloud platform through communication links between the APP and the cloud platform:

{

"CMD": "ADD_NEW_MESH_NODE",

"BUSINESS_NO": "MESH_010000101",

“SEQ”:01

}

after the cloud platform receives the request, immediately replying to a received command, indicating that the request is received, and currently entering an initialization state:

{

"BUSINESS_NO": " MESH_010000101",

"STATUS": "INIT",

“SEQ”:02

}

further, in step 2, the timeout time is generally set to 60 seconds, the polling interval is once every 1 second, and the query instruction is:

{

"CMD": QUERY_MESH_RESULT",

"BUSINESS_NO": "MESH_010000101",

“SEQ”:03

}

{

"RESP": MESH_RESULT",

"BUSINESS_NO": "MESH_010000101",

“SEQ”:04,

“STATUS”:”PROCESSING”

}

when the user wishes to cancel the networking operation in advance, the user can click a cancel button. At this moment, triggering the APP to send a cancel instruction to the cloud platform:

{

"CMD": "CANCEL_MESH",

“SEQ”:05

}

when canceling, the cloud platform replies a canceling result:

{

"RESP": CANCEL_MESH_RESULT",

"BUSINESS_NO": "MESH_010000101",

“SEQ”:06,

“STATUS”:”CALCELED”

}

in step 3, if the failure occurs, further, a detailed failure reason may be determined and a prompt may be generated, including but not limited to: 1. the new MESH node is not detected as present, and the new MESH node is confirmed to be powered up and retried later. 2. The new MESH node is not in the effective range of the signal intensity of any online equipment, and the distance between the new MESH node and the online equipment is recommended not to exceed 5 meters. 3. And refusing new access because the load of the existing online equipment reaches the upper limit, and suggesting to expand the existing network wireless equipment. 4. Because the versions of the existing online devices are not matched, the access cannot be supported, and the existing network devices are recommended to be upgraded.

After the cloud platform receives a request of adding a new MESH device from the APP, the cloud platform starts to work for adding a new node. The workflow of the cloud platform is described below.

3. And adding a new node flow by the cloud platform.

1. Initializing a database

The cloud platform and the APP have a communication link, and after the APP sends a request to the cloud platform, the cloud platform needs to perform work of coordinating online equipment to access a new MESH node except for responding to the request. This process is asynchronous, and in the process of coordinating and completing networking by the entire cloud platform, the APP polls the cloud platform at a frequency of once per second, and the cloud platform may be random because of the distributed deployment, the cloud service machine receiving the poll. Therefore, whether networking is successful or not is achieved by concentrating the results in a database, and all cloud services uniformly call database query statements to retrieve networking results. And if the result is inquired, returning the result to the APP.

After receiving the request, the cloud platform firstly initializes the record of the database, and stores the networking result into a table 'mesh _ result' in a database mode, wherein the table field comprises:

the networking message service number means that when the cloud platform receives a networking adding request, the APP generates a service number for the service, and the number is used for retrieving a subsequent networking result;

the networking processing result comprises the following conditions: INIT: initializing, namely entering the state when an AP (access point) networking starting command is just received, and entering a negotiation working state by the cloud platform; PROCESSING, wherein the command is issued to the optimal APP to wait for the completion of PROCESSING; SUCCESS, the best APP is successfully accessed to the new MESH node, and the time consumption is recorded; TIMEOUT, namely overtime processing and time consumption recording; CANCEL client, recording time; FAILED, record failure reason code and time.

The failure reason code includes: ERR001, no new MESH node exists, please confirm if the new MESH node is powered up and retry later. ERR002, new MESH node is not in any online equipment signal intensity effective range, suggest new MESH node distance online equipment not more than 5 meters distance. ERR003, because the load of the existing online equipment reaches the upper limit reason, refuse the new access, propose the dilatation existing network wireless device. ERR004, because the versions of the existing online devices are not matched, the access can not be supported, and the upgrading of the existing network devices is recommended.

2. Selecting the best AP

After the initialization of the table entry of the MESH networking result database is completed, the cloud platform starts the selection process of the optimal AP, and the process is as follows:

step 1, the cloud platform checks a data acquisition table in the following form and carries out algorithm judgment. In the data collection table, the creation time is the creation time recorded when reporting the data reported by the AP. And the updating time is the time for reporting the RSSI value of the MESH node discovered by the AP to update. And (3) status code: 1-indicates that the record is valid; 2-indicating that the record is invalid, and when the new MESH node completes networking, the state is set to invalid. Or the networking is overtime, and the state is set to be invalid.

Step 2, the cloud platform checks the table, if the valid record is empty, and no online AP reports the detection of the MESH node, the process is ended, an error code ERR001 is recorded, and the APP is responded to: please check if the new MESH node is powered up normally and retries later.

Step 3, on the premise of effective recording, the cloud platform further traverses each state in the data acquisition table to obtain effective data, and the algorithm logic of the process can be as follows: 1. if the RSSI is lower than the minimum requirement, the method is directly finished, and the error code ERR002 is recorded. 2. And if the load of each AP exceeds the upper limit, ending the process and recording the error code ERR003. 3. If the version of the AP is lower than the set version number, the process is ended, and the error code ERR004 is recorded. 4. The cloud platform will further check for topological relationships, if wired upstream, as preferred. 5. In the same topology, the load is preferably light. 6. When the load level is equivalent, the RSSI is preferably strong.

Here, regarding the load LEVEL determination, the number of on-line terminals is used as a measure, for example, the number of on-line terminals < =15 is LEVEL1, which indicates that the load is light. The number of the on-line terminals is 16-25, LEVEL2, and the load is moderate. The number of the on-line terminals is 25-40, namely LEVEL3, and the load is heavier. The number of terminals on line is LEVEL4 at 41-64, which is heavily loaded. The number of the on-line terminals is 64 as the upper limit, and the wireless MESH nodes can not be accessed any more when the upper limit is reached.

Wherein, regarding the topological relation, the data generation and change situation is as follows: and dividing wired uplink and wireless uplink, and checking whether a WAN port is used or not by the equipment, wherein if the WAN port is used, wired uplink is performed, and otherwise, wireless uplink is performed. The change of the topological relation is actively triggered by the AP to be reported to the cloud platform and recorded in the following data acquisition table:

in the data acquisition table, 1, AP MAC is reported MAC of AP, 2, wireless MESH superior, when AP forms MESH network with superior through wireless, recording MAC of superior AP, 3, whether wired access exists, 1 is wired access, 0 is wireless access; in the present case, the MAC of the wireless router 10: 18 bd 67: 18 bd. Further, the data collection table is generated by reporting to the cloud platform by the online device (the wireless router 10 and the MESH node 1 30) after a series of interactions by the wireless router 10, the MESH node 1 30, and the MESH node 2. The interaction process comprises the following steps: after MESH node 2 powers up, it issues a PROBE REQUEST frame to find the best AP to "cater" for its access. Both the wireless router 10 and the MESH node 1 30 hear this PROBE REQUEST and report to the cloud platform. And the cloud platform receives the reported data and records the reported data to the database, so that the data acquisition table is generated.

According to the above description, the data is collected by the online AP, the collection object is the newly added wireless MESH node, and the collection result is stored in a data collection table of the cloud platform. The specific flow of data acquisition is described below.

4. And (5) data acquisition process.

In the present embodiment, MESH node 2 40, which is the object to join the MESH network, undergoes the following MESH lookup and join procedure after power up: step 1, electrifying, wherein the state is not configured; step 2, judging that the WAN port is not plugged with a network cable, and starting to broadcast and search the PROBE REQUEST of the MESH network, wherein the REQUEST and the RESPONE are characterized in that: 1. with special identification, can be recognized by the neighbors and is extended in the information element part. 2. If the neighbor has a PROBE RESPONSE with a reply that also carries a special identity, the connection to the radio can begin. 3. If the received is not a normal PROBE RESPONSE with a special identity, it is ignored. 4. The special identification is as follows: the PROBE REQUEST is used as a management frame, and in the information elements carried by the management frame, a reserved element with the serial number of 15 is used as a private mark, the length of the reserved element is 1, the value of the reserved element is 1, and the reserved element represents searching for the MESH neighbor. And taking an element with the number of 14 as a response, wherein the length is 1, the value is 2, and the neighbor is represented.

In this embodiment, after the PROBE REQUEST sent by MESH node 2 40 is received by wireless router 10 and MESH node 1 30, the two receiving APs will recognize that there is a new MESH node to join the MESH network. At this time, the two online APs report the data to the cloud platform. Further, the reported data further includes the collected signal strength information of the new MESH node and the MAC address of the new MESH node. Based on the data, the cloud platform records the relevant data of the data acquisition table and waits for the APP to initiate the MESH networking action. Finally, when the best AP (in this embodiment, the best AP is the wireless router 10, since the uplink is wired, and it is assumed that the signal strength of the join signal received by the wireless router 10 is within the allowed range) receives the indication of "accessing to the new MESH node" issued by the cloud platform, the best AP replies the request RESPONSE to the new MESH node. The wireless router 10 thus opens a tunnel for establishing a MESH connection. Through the above steps, the MESH node 2 may finally select the wireless router 10 as the upper level, complete the MESH access, and form the channel of "cloud platform 20-internet-wireless router 10-wireless network-MESH node 2 40".

5. And automatic routing flow after the intermediate node is disconnected.

Considering the situation that the MESH network has node disconnection, in some embodiments, when the access point is disconnected, the device to be added to the MESH network resends the join request, so that the cloud platform re-determines the access point according to the received request information; for example, when the upper node is disconnected, the device resends the PROBE REQUEST, and after the REQUEST for rejoining the MESH is received by the neighbor, the cloud platform is automatically triggered to reselect the best access point. Therefore, after the intermediate node disconnects the AP, the method also has the capability of automatically converging to a proper upper level, and further reduces the burden of operation and maintenance.

In the present embodiment, it is assumed that initially MESH node 2 and MESH node 1 30 form a MESH network due to a certain condition, that is, the uplink channel is "cloud platform 20-internet-wireless router 10-wireless network-MESH node 1-MESH node 2 30-MESH node 2 40", and MESH node 1 30 fails during operation. At this time, MESH node 2 40 re-searches wireless router 10 by: step 1, the MESH node 2 40 checks the long-time disconnection of the uplink, and judges the occurrence of the wireless MESH upper stage fault. Step 2, the MESH node 2 40 triggers to resend PROBE REQUEST to search the upper level, and carries a re-search mark which is different from the initial neighbor discovery mark, wherein the IE information ID is 13, the length is 1, and the value is 03. And 3, the wireless router 10 receives the re-search command, reports the re-search command to the cloud platform, and the cloud platform commands the wireless router 10 to open the access channel and reply a re-access response to the MESH node 2, wherein the response is different from the access response in the configuration stage, and the IE information ID is 12, the length is 1 and the value is 04. And step 4, the wireless router 10 further opens a related SSID, and the MESH node 2 is accessed to form a new MESH node and topological relation, so as to form a channel of the cloud platform 20-Internet-wireless router 10-wireless network-MESH node 2 40. This procedure does not require APP intervention.

In combination with the MESH networking method in the foregoing embodiment, the embodiment of the present application may provide a storage medium to implement. The storage medium having stored thereon a computer program; when executed by a processor, the computer program implements any MESH networking method in the foregoing embodiments.

In one embodiment, a computer device is provided, which may be a terminal. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operating system and the computer program to run on the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a MESH networking method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

In an embodiment, fig. 6 is a schematic internal structure diagram of an electronic device according to an embodiment of the present application, and as shown in fig. 6, there is provided an electronic device, which may be a server, and its internal structure diagram may be as shown in fig. 6. The electronic device includes a processor, a network interface, an internal memory, and a non-volatile memory, which stores an operating system, a computer program, and a database, connected by an internal bus. The processor is used for providing calculation and control capabilities, the network interface is used for being connected and communicated with an external terminal through a network, the internal memory is used for providing an environment for an operating system and the running of a computer program, the computer program is executed by the processor to realize a MESH networking method, and the database is used for storing data.

It will be appreciated by those skilled in the art that the structure shown in fig. 6 is a block diagram of only a portion of the structure associated with the present application, and does not constitute a limitation on the electronic device to which the present application applies, and that a particular electronic device may include more or fewer components than shown, or combine certain components, or have a different arrangement of components.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above may be implemented by hardware instructions of a computer program, which may be stored in a non-volatile computer-readable storage medium, and when executed, the computer program may include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), rambus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

It will be appreciated by persons skilled in the art that for simplicity of explanation, not all possible combinations of features described in the above embodiments are described, but rather the scope of the description is to be construed as being without limitation to such combinations.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A MESH networking method, characterized in that the method comprises:

2. The method of claim 1, wherein before the cloud platform determines an access point, the method further comprises: the cloud platform receives a decision starting instruction issued by the user side, and executes a decision in response to the decision starting instruction to determine the access point.

3. The method according to claim 1, wherein the cloud platform determines the access point according to a received request information comprehensive decision reported by the devices in the plurality of MESH networks, and the process comprises:

the cloud platform traverses each state to be effective data in the received request information, and comprehensively decides to determine an access point; and the cloud platform sets the state of the corresponding data to be invalid under the condition that the equipment outside the MESH network finishes networking or the networking is overtime.

4. The method of claim 1, wherein the cloud platform determines the access point based on a received request information comprehensive decision reported by the devices in the plurality of MESH networks, and the process comprises:

5. The method of claim 1, wherein the access point accesses a device outside the MESH network, comprising:

6. The method of claim 1, further comprising:

after the equipment to be added to the MESH networking is started, the equipment to be added to the MESH networking sends the adding request in a broadcasting mode, or under the condition that the access point is disconnected, the equipment to be added to the MESH networking resends the adding request, so that the cloud platform can determine the access point again according to the received request information.

7. A MESH networking system, the system comprising: the system comprises a cloud platform, equipment in the MESH network and equipment outside the network to be added into the MESH network;

under the condition that equipment in each MESH network receives a joining request sent by equipment outside the MESH network, reporting request information to a cloud platform for decision making of the cloud platform;

8. The system of claim 7, wherein the cloud platform determines the access point based on a received request information comprehensive decision reported by the devices in the plurality of MESH networks, and the process comprises:

9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to perform the MESH networking method of any one of claims 1 to 6.

10. A storage medium having a computer program stored therein, wherein the computer program is configured to execute the MESH networking method of any one of claims 1 to 6 when executed.