CN113950120A - Equipment networking method and device, terminal equipment and readable storage medium - Google Patents

Equipment networking method and device, terminal equipment and readable storage medium Download PDF

Info

Publication number
CN113950120A
CN113950120A CN202111199735.8A CN202111199735A CN113950120A CN 113950120 A CN113950120 A CN 113950120A CN 202111199735 A CN202111199735 A CN 202111199735A CN 113950120 A CN113950120 A CN 113950120A
Authority
CN
China
Prior art keywords
cascade
networking
equipment
connection information
slave
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111199735.8A
Other languages
Chinese (zh)
Inventor
余波
宋向辉
方亭亭
李尹丹
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Chengdu Kangte Electronic Technology Co ltd
Original Assignee
Chengdu Kangte Electronic Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Chengdu Kangte Electronic Technology Co ltd filed Critical Chengdu Kangte Electronic Technology Co ltd
Priority to CN202111199735.8A priority Critical patent/CN113950120A/en
Publication of CN113950120A publication Critical patent/CN113950120A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • H04W40/24Connectivity information management, e.g. connectivity discovery or connectivity update
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/18Self-organising networks, e.g. ad-hoc networks or sensor networks
    • H04W84/20Master-slave selection or change arrangements

Abstract

The application provides a device networking method and device, terminal equipment and a readable storage medium, and relates to the technical field of wireless networking. According to the method, for each slave end device in the MESH routing system, based on the cascade routing relation, recorded by cascade networking connection information stored by the slave end device, from a master end device to a corresponding tail end cascade device in the MESH routing system, the tail end cascade device is selected as the current cascade device to be connected of the slave end device, and then networking connection is established with the cascade device to be connected in a specific time period, so that each slave end device is networked according to the respective device routing relation, wireless networking operation with strong routing condition stability is realized, and the influence of network fluctuation on a wireless networking result is reduced. Meanwhile, when the slave end equipment cannot be connected to the corresponding cascade equipment to be connected, other effective cascade equipment and the slave end equipment are replaced in time to carry out networking, so that the routing system can be successfully networked.

Description

Equipment networking method and device, terminal equipment and readable storage medium
Technical Field
The present application relates to the field of wireless networking technologies, and in particular, to a device networking method and apparatus, a terminal device, and a readable storage medium.
Background
With the continuous development of network technology, wireless networking technology is applied to various industries because of the capability of building wireless local area networks, and people correspondingly put forward more requirements on the wireless networking technology, wherein the MESH networking technology is an important technical branch of the wireless networking technology. At present, the existing MESH networking technology is directly realized based on the distribution condition of signal intensity in a communication environment during each networking, so that the randomness of the obtained networking result is high, the stability of the overall network routing condition is not strong, and the influence of network fluctuation is high.
Disclosure of Invention
In view of the above, an object of the present application is to provide a device networking method and apparatus, a terminal device, and a readable storage medium, which can implement wireless networking operation with strong stability of routing status and reduce the influence of network fluctuation on a wireless networking result.
In order to achieve the above purpose, the embodiments of the present application employ the following technical solutions:
in a first aspect, the present application provides a device networking method, which is applied to each slave device included in a MESH routing system, where the MESH routing system further includes a master device, and the method includes:
reading cascade networking connection information stored in the slave end equipment, wherein the cascade networking connection information records a cascade routing relation from the master end equipment to corresponding tail end cascade equipment;
selecting the terminal cascade equipment corresponding to the cascade routing relation as the current cascade equipment to be connected of the slave end equipment;
and establishing networking connection with the cascade equipment to be connected within a time period corresponding to the preset time length.
In an optional implementation manner, the cascade networking connection information further records a cascade networking hierarchy of the corresponding end cascade device relative to the master device, and the method further includes:
the method comprises the steps that networking connection cannot be established with the cascade equipment to be connected within a time period corresponding to preset time length, and the cascade equipment to be connected is removed from the cascade routing relation under the condition that the cascade networking hierarchy in cascade networking connection information is not empty, so that a corresponding first cascade relation is obtained;
and selecting all cascade equipment in a reverse order according to the equipment cascade sequence of the first cascade relation, and establishing networking connection with the cascade equipment in a time period corresponding to a preset time length aiming at the selected single cascade equipment in sequence until the networking connection with certain cascade equipment is successfully established.
In an alternative embodiment, the method further comprises:
receiving return connection information from the last cascade equipment currently connected with the slave end equipment;
and performing content replacement on the cascade networking connection information stored in the slave end equipment by adopting the received return connection information.
In an alternative embodiment, the method further comprises:
generating backhaul connection information for the slave end device on the basis of the cascade networking connection information stored by the slave end device, wherein the backhaul connection information records a second cascade relationship from the master end device to the slave end device and a cascade networking hierarchy of the slave end device relative to the master end device;
and sending the returned connection information of the slave end equipment to the next cascade equipment currently connected with the slave end equipment as the cascade networking connection information of the next cascade equipment for storage.
In a second aspect, the present application provides an apparatus networking device, which is applied to each slave device included in a MESH routing system, where the MESH routing system further includes a master device, and the apparatus further includes:
the cascade information reading module is used for reading cascade networking connection information stored in the slave end equipment, wherein the cascade networking connection information records a cascade routing relation from the master end equipment to the corresponding tail end cascade equipment;
a connection device selection module, configured to select a terminal cascade device corresponding to the cascade routing relationship as a current cascade device to be connected to the slave device;
and the networking connection establishing module is used for establishing networking connection with the cascade equipment to be connected within a time period corresponding to the preset time length.
In an optional implementation manner, the cascade networking connection information further records a cascade networking hierarchy of the corresponding end cascade device relative to the master device, and the apparatus further includes:
the cascade connection relation generating module is used for removing the cascade equipment to be connected in the cascade routing relation under the condition that the cascade networking connection with the cascade equipment to be connected cannot be established within the time period corresponding to the preset time length and the cascade equipment to be connected is not empty in the cascade networking connection information, so as to obtain a corresponding first cascade relation;
and the networking connection establishing module is further used for selecting all the cascade equipment in reverse order according to the equipment cascade sequence of the first cascade relation, and establishing networking connection with the cascade equipment in a time period corresponding to the preset time length aiming at the selected single cascade equipment in sequence until the networking connection with certain cascade equipment is successfully established.
In an alternative embodiment, the apparatus further comprises:
a backhaul connection receiving module, configured to receive backhaul connection information from a previous tandem device to which the slave device is currently connected;
and the cascade information replacement module is used for performing content replacement on the cascade networking connection information stored in the slave equipment by adopting the received returned connection information.
In an alternative embodiment, the apparatus further comprises:
a backhaul connection generation module, configured to generate backhaul connection information for the slave device on the basis of the cascade networking connection information stored in the slave device, where the backhaul connection information records a second cascade relationship from the master device to the slave device, and a cascade networking hierarchy of the slave device relative to the master device;
and the return connection sending module is used for sending the return connection information of the slave end equipment to the next cascade equipment currently connected with the slave end equipment as the cascade networking connection information of the next cascade equipment for storage.
In a third aspect, the present application provides a terminal device, configured to serve as a slave device included in a MESH routing system, except for a master device, where the terminal device includes a processor and a memory, where the memory stores a computer program that can be executed by the processor, and the processor can execute the computer program to implement the device networking method in any one of the foregoing embodiments.
In a fourth aspect, the present application provides a readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the device networking method according to any one of the foregoing embodiments.
In this case, the beneficial effects of the embodiments of the present application include the following:
the method comprises the steps that for each slave end device in the MESH routing system, cascade networking connection information stored by the slave end device is read, the cascade routing relation from a master end device to the corresponding tail end cascade device in the MESH routing system is recorded based on the cascade networking connection information, the tail end cascade device corresponding to the cascade routing relation is selected as the current cascade device to be connected of the slave end device, and then networking connection is established with the corresponding cascade device to be connected in the time period corresponding to the preset time length, so that each slave end device in the same MESH routing system can be enabled to perform networking according to the specific device routing relation, wireless networking operation with strong routing condition stability is achieved, and the influence of network fluctuation on a wireless networking result is reduced.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic composition diagram of a terminal device provided in an embodiment of the present application;
fig. 2 is a flowchart of a device networking method according to an embodiment of the present application;
fig. 3 is a second flowchart of a device networking method according to an embodiment of the present application;
fig. 4 is a third schematic flowchart of a device networking method according to an embodiment of the present application;
fig. 5 is a fourth flowchart illustrating an apparatus networking method according to an embodiment of the present application;
fig. 6 is a schematic composition diagram of an apparatus networking device according to an embodiment of the present application;
fig. 7 is a second schematic diagram illustrating a networking apparatus according to an embodiment of the present application;
fig. 8 is a third schematic composition diagram of an apparatus networking device according to an embodiment of the present application;
fig. 9 is a fourth schematic composition diagram of an apparatus networking device according to an embodiment of the present application.
Icon: 10-a terminal device; 11-a memory; 12-a processor; 13-a communication unit; 100-device networking means; 110-a cascade information reading module; 120-connecting device selection module; 130-networking connection establishment module; 140-a cascade relation generating module; 150-backhaul connection receiving module; 160-a cascade information replacement module; 170-backhaul connection generation module; 180-backhaul connection sending module.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
In the description of the present application, it is to be understood that relational terms such as the terms first and second, and the like, are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element. The specific meaning of the above terms in the present application can be understood in a specific case by those of ordinary skill in the art.
Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and the features of the embodiments can be combined with each other without conflict.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating a terminal device 10 according to an embodiment of the present disclosure. In this embodiment, the terminal device 10 may be configured to serve as a slave device included in a MESH routing system except for a master device, where the number of the slave devices included in the MESH routing system is at least two, the master device is configured to represent a central control center in the MESH routing system, and each slave device in the MESH routing system needs to be directly connected with the master device or indirectly connected with the master device through other slave devices, so as to obtain a wireless networking result corresponding to the MESH routing system. The main end device included in the MESH routing system may also be served by a certain terminal device 10.
In this embodiment, when performing the initialization networking arrangement on the MESH routing system, it is necessary to determine an initial cascade relationship between any two devices (including a master device and a certain slave device, or a certain slave device and another slave device) that need to be directly connected in the MESH routing system, and then establish networking connections between the two corresponding devices based on all the determined initial cascade relationships, so as to complete the initialization networking of the MESH routing system. The initial cascade relationship may be configured by a manager of the MESH routing system according to a need of the manager, on the basis of selecting the master device in the MESH routing system, for any two devices that need to be directly connected, in the master device and all slave devices included in the MESH routing system. The initial cascade relationship may also be directly set by the manufacturer as the master device and the slave device in the production process of the MESH routing system, and the manufacturer directly configures any two devices from these devices.
The initial cascade relationship is used to represent respective up-down cascade roles of the two corresponding devices in the initial arrangement, that is, whether the two corresponding devices are respectively an upper cascade device or a lower cascade device relative to the other device in the initial arrangement. For an initial cascade relationship between a master device and a slave device, the master device needs to be set as a cascade device above the slave device in the initial cascade relationship.
In an implementation manner of this embodiment, the MESH routing system may include a master device and each slave device, each of which may be provided with a networking key (e.g., an entity key, and a virtual key on a control interface). When a manager or a manufacturer configures the corresponding initial cascade relationship for two devices that need to be directly connected, the networking button of one of the two devices that needs to be the previous cascade device may be pressed first, and then the networking button of one of the two devices that needs to be the next cascade device may be pressed, thereby completing the configuration operation for the initial cascade relationship between the two devices.
In addition, after the MESH routing system successfully completes one wireless networking operation, each device (including a master device and any one slave device) in the MESH routing system generates corresponding backhaul connection information according to the cascade connection status from the master device to the device and the cascade networking hierarchy of the device relative to the master device, and sends the generated backhaul connection information to the next-level-connected device of the device, so that the next-level-connected device stores the received backhaul connection information as the cascade networking connection information of the next-level-connected device.
For each slave device in the MESH routing system, the cascade networking connection information stored by the slave device may be used to indicate a cascade routing status from the master device to the currently configured upper cascade device, and a cascade networking hierarchy of the currently configured upper cascade device with respect to the master device, at this time, the backhaul connection information of the slave device may be generated by adding relevant information of the slave device to the cascade networking connection information stored by the slave device, where the relevant information includes identity information of the corresponding slave device and the cascade networking hierarchy of the slave device with respect to the master device.
Therefore, when the MESH routing system needs to be re-networked due to physical factors such as power failure or signal shielding, each slave device in the MESH routing system executes related operations required for establishing networking connection to the currently configured upper-level networking device based on the cascade networking connection information stored by the slave device, so as to try to establish networking connection between the slave device and the currently configured upper-level networking device, ensure that the finally constructed routing condition of the wireless networking result has stronger stability, and reduce the influence degree of network fluctuation on the wireless networking result.
In this process, the cascaded networking hierarchy is used to represent the number of cascaded links that data needs to go through to transmit from the corresponding device to the master end device. For the master device, if the number of cascaded links that the corresponding data needs to undergo to be transmitted from the corresponding device to the master device is zero, the cascaded networking hierarchy corresponding to the master device is empty, and the cascaded connection status recorded in the backhaul connection information corresponding to the master device only records the identity information of the master device.
In an implementation manner of this embodiment, the identity information of the master Device may be represented by an ESSID (Extended Service Set Identifier) of the wireless local area network that needs to be constructed, the identity information of each slave Device may be represented by at least two consecutive characters in a Unique Device Identifier (Unique Device ID) corresponding to the slave Device (for example, corresponding to a MAC address of the slave Device), at this time, a cascade connection status corresponding to the backhaul connection information of each Device in the MESH routing system may be expressed by a character string formed by connecting, by using an interval symbol, the identity information of each Device in cascade connection related to the cascade connection status, and a tail of the character string formed by using the interval symbol is immediately followed by a cascade connection level networking level of the Device relative to the master Device.
Taking an MESH routing system including a master device C, a slave device a and a slave device B as an example, if the master device C is used as a cascade device above the slave device a, the slave device a is used as a cascade device above the slave device B, the identity information of the master device C is ESSID-C, the identity information of the slave device a is AA, the identity information of the slave device B is BB, the cascade networking level of the master device C is null, the cascade networking level of the slave device a is T1, the cascade networking level of the slave device B is T1, and the backhaul networking connection information of the master device C is used as the cascade networking connection information of the slave device a and can be expressed as "ESSID-C"; the backhaul connection information of the slave device a will be referred to as the tandem networking connection information of the slave device B, and may be denoted as "ESSID-C-AA-T1"; the backhaul connection information from the end device B may be denoted as "ESSID-C-AA-BB-T2".
In this embodiment, the terminal device 10 may include a memory 11, a processor 12, a communication unit 13, and a device networking apparatus 100, where the device networking apparatus 100 is configured to implement a wireless networking operation with strong routing condition stability when the terminal device 10 is used as a slave device. The various elements of the memory 11, the processor 12 and the communication unit 13 are electrically connected to each other directly or indirectly to realize data transmission or interaction. For example, the memory 11, the processor 12 and the communication unit 13 may be electrically connected to each other through one or more communication buses or signal lines.
In this embodiment, the Memory 11 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like. The memory 11 is used for storing a computer program, and the processor 12 can execute the computer program after receiving an execution instruction. The memory 11 is further configured to store currently configured cascade networking connection information when the terminal device 10 is used as a slave device, where the cascade networking connection information records a cascade routing relationship from a master device to a terminal cascade device corresponding to the cascade networking connection information, and a cascade networking hierarchy of the terminal cascade device relative to the master device. For a slave device, the end cascade device corresponding to the cascade networking connection information stored in the slave device is substantially equivalent to the previous cascade device configured for the slave device. When the terminal device 10 is re-networked as a slave device, based on the cascade networking connection information stored in the terminal device 10, the terminal device may execute the relevant operations required for establishing the networking connection to the currently configured upper cascade device (including other slave devices or the master device) of the terminal device 10.
In this embodiment, the processor 12 may be an integrated circuit chip having signal processing capabilities. The Processor 12 may be a general-purpose Processor including at least one of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Network Processor (NP), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, and discrete hardware components. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like that implements or executes the methods, steps and logic blocks disclosed in the embodiments of the present application.
In this embodiment, the communication unit 13 is configured to establish a communication connection between the terminal device 10 and other electronic devices, where the other electronic devices include a mobile terminal, the above-mentioned master device or other slave devices, and the like.
In this embodiment, the device networking apparatus 100 includes at least one software functional module that can be stored in the memory 11 or in the operating system of the terminal device 10 in the form of software or firmware. The processor 12 may be used to execute executable modules stored in the memory 11, such as software functional modules and computer programs included in the device networking apparatus 100. When the terminal device 10 is used as a slave device of the MESH routing system, the device networking apparatus 100 can implement wireless networking operation with strong routing condition stability, reduce the influence of network fluctuation on the wireless networking result, and improve the stability of the reorganization network of the MESH routing system in which the terminal device 10 is located.
It is understood that the block diagram shown in fig. 1 is only one constituent schematic diagram of the terminal device 10, and the terminal device 10 may further include more or less components than those shown in fig. 1, or have a different configuration from that shown in fig. 1. The components shown in fig. 1 may be implemented in hardware, software, or a combination thereof.
In this application, in order to ensure that the terminal device 10 can implement wireless networking operation with strong routing status stability when serving as a slave device of the MESH routing system, reduce the influence of network fluctuation on a wireless networking result, and improve the stability of a reorganization network of the MESH routing system, the embodiment of the present application implements the foregoing functions by providing a device networking method applied to a slave device included in the MESH routing system, and the device networking method provided in the present application is described in detail below.
Referring to fig. 2, fig. 2 is a flowchart illustrating a device networking method according to an embodiment of the present disclosure. In this embodiment, the device networking method shown in fig. 2 may include step S210 to step S230, so that each slave device in the same MESH routing system can perform networking according to a specific device routing relationship, thereby implementing wireless networking operation with strong routing condition stability, reducing the influence of network fluctuation on a wireless networking result, and improving the stability of a recombinant network of the MESH routing system.
Step S210, reading the cascade networking connection information stored in the slave device, where the cascade networking connection information records a cascade routing relationship from the master device to the corresponding end cascade device.
In this embodiment, when participating in a networking process as a slave device, the terminal device 10 needs to read cascade networking connection information stored in itself, and extract a cascade routing relationship from a master device to a corresponding end cascade device from the cascade networking connection information, where the cascade routing relationship is used to indicate a cascade path from the master device to the corresponding end cascade device. Taking the above-mentioned cascade networking connection information "ESSID-C-AA-T1" of the slave device B as an example, the cascade routing relationship corresponding to the cascade networking connection information is "ESSID-C-AA", that is, the cascade routing relationship directly from the master device C to the slave device a.
Step S220, selecting the end cascade device corresponding to the cascade routing relationship as the current cascade device to be connected of the slave device.
In this embodiment, when a certain slave device reads a cascade routing relationship from the master device to a corresponding end cascade device from cascade networking connection information stored in the slave device, the end cascade device corresponding to the cascade routing relationship may be regarded as a previous cascade device that needs to be connected and is currently configured for the slave device, and the end cascade device is the current cascade device to be connected of the slave device. Taking the cascade networking connection information "ESSID-C-AA-T1" of the slave device B as an example, the end cascade device of the cascade routing relationship corresponding to the cascade networking connection information is the slave device a, and at this time, the slave device a is the current cascade device to be connected of the slave device B (i.e., the configured previous cascade device to be connected); taking the cascade networking connection information "ESSID-C" -of the slave device a as an example, the tail-end cascade device of the cascade routing relationship "ESSID-C" corresponding to the cascade networking connection information is the master device C, and at this time, the master device C is the current cascade device to be connected of the slave device a.
Step S230, establishing a networking connection with the cascade device to be connected within a time period corresponding to the preset time duration.
In this embodiment, after a certain slave device determines its current cascade device to be connected, the time at which the cascade device to be connected is determined is taken as a starting time point of networking connection, and a networking connection establishment operation is performed with the cascade device to be connected at a specific time interval within a time period corresponding to a preset time duration, so that a networking connection between itself and the cascade device to be connected is continuously attempted to be established within the time period corresponding to the preset time duration, and each slave device in the same MESH routing system can perform networking according to a specific device routing relationship, thereby implementing wireless networking operation with strong routing condition stability, reducing the influence of network fluctuation on a wireless networking result, and improving the stability of a recombinant network of the MESH routing system. The duration corresponding to the preset time interval is less than the preset duration, and the duration corresponding to the preset time interval is a divisor of the preset duration. In one implementation of this embodiment, the preset time period is set to 3 minutes, and the preset time interval is set to 10 seconds.
Therefore, by executing the steps S210 to S230, each slave device in the same MESH routing system can perform networking according to a specific device routing relationship, thereby implementing wireless networking operation with strong routing condition stability, reducing the influence of network fluctuation on a wireless networking result, and improving the stability of a recombined network of the MESH routing system.
Optionally, referring to fig. 3, fig. 3 is a second flowchart of the device networking method according to the embodiment of the present application. In this embodiment, compared with the device networking method shown in fig. 2, the device networking method shown in fig. 3 may further include step S240 to step S250, which are used to replace an effective connectable cascade device in time for networking when the corresponding slave device cannot be connected to the currently configured to-be-connected cascade device, so as to ensure that the MESH routing system where the slave device is located can be completely and successfully networked. And the cascade networking connection information stored by each slave end device also records the cascade networking level of the corresponding tail end cascade device relative to the master end device.
Step S240, when the networking connection with the to-be-connected cascade device is not established within the time period corresponding to the preset time length and the cascade device to be connected is not in the cascade networking hierarchy in the cascade networking connection information, removing the to-be-connected cascade device in the cascade routing relationship, and obtaining the corresponding first cascade relationship.
In this embodiment, if the cascade networking level of the to-be-connected cascade device currently corresponding to a certain slave device in the corresponding cascade networking connection information is empty, it may represent that the to-be-connected cascade device currently corresponding to the slave device is a master device, at this time, if the slave device fails to be successfully connected with the master device, the connectable device of the slave device also only includes the master device, and the slave device can only continue to establish networking connection with the master device until the connection is successful.
If a certain slave end device fails to establish networking connection with the currently corresponding cascade device to be connected within the time period corresponding to the preset time length, and the cascade device to be connected has no cascade networking hierarchy in the corresponding cascade networking connection information, that is, the cascade device to be connected may be substantially other slave end devices in the MESH routing system, at this time, other cascade devices (at least including the master end device) except the cascade device to be connected in the cascade routing relationship in which the cascade device to be connected is located may be used as connectable devices of the slave end device, at this time, the identity information of the cascade device to be connected in the cascade routing relationship may be directly removed, so as to obtain a corresponding first cascade relationship, at this time, the tail end cascade device in the first cascade relationship is the penultimate cascade device in the cascade routing relationship.
Taking the slave device D as an example for explanation, if the cascade networking connection information stored by the slave device D is "ESSID-C-AA-BB-T2", the to-be-connected cascade device of the slave device D is the slave device B, if the slave device D cannot establish networking connection with the slave device B within the time period corresponding to the preset time duration, the first cascade relationship corresponding to the slave device D at this time may be denoted as "ESSID-C-AA", and the master device C and the slave device a are connectable cascade devices of the slave device D.
And step S250, selecting all cascade equipment in reverse order according to the equipment cascade sequence of the first cascade relation, and establishing networking connection with the cascade equipment in a time period corresponding to the preset time length aiming at the selected single cascade equipment in sequence until the networking connection with certain cascade equipment is successfully established.
In this embodiment, after a current corresponding first cascade relation is determined for a certain slave device, a device cascade order of the first cascade relation is determined, all cascade devices corresponding to the device cascade order are sequentially selected in reverse order, and for a single selected cascade device at each time, networking connection with the cascade device is established at a preset time interval within a time period corresponding to a preset time duration until the slave device successfully establishes networking connection with a certain cascade device of at least one cascade device corresponding to the first cascade relation. Each selected cascade device corresponds to a time period with preset time length required for trying to establish networking connection with the slave device.
Taking the first cascade relation corresponding to the slave device D as "ESSID-C-AA" as an example, the device cascade order corresponding to the first cascade relation is that the next cascade device of the master device C is the slave device a, and at this time, it is necessary to try to establish the networking connection between the slave device D and the slave device a within a time period of a preset time duration. If the networking connection between the slave end device D and the slave end device a is not successfully established, trying to establish the networking connection between the slave end device D and the master end device C within a time period of preset time duration until the networking connection between the slave end device D and the master end device C is successfully established.
Therefore, by executing the steps S240 to S250, the method and the device enable the corresponding slave device to timely replace the effectively connectable cascade device for networking when the currently configured cascade device to be connected cannot be connected, so as to ensure that the MESH routing system where the slave device is located can be completely and successfully networked.
Optionally, referring to fig. 4, fig. 4 is a third flowchart illustrating a device networking method according to an embodiment of the present application. In this embodiment, compared with the device networking method shown in fig. 3, the device networking method shown in fig. 4 may further include step S260 and step S270, where the step S270 is configured to update the device routing status of the to-be-connected cascade device stored on each slave device in time when the MESH routing system completes networking, and solidify the wireless networking result of the MESH routing system in time, so as to improve the stability of the reorganization network of the MESH routing system.
Step S260, receiving backhaul connection information from the last tandem device currently connected from the end device.
In this embodiment, when a certain slave device successfully establishes a networking connection with a corresponding previous tandem device (which may be a master device or a certain slave device), a current previous tandem device of the slave device may generate backhaul connection information of the previous tandem device based on a status of a cascade path from the master device to the previous tandem device, where the backhaul connection information of the previous tandem device records a device cascade relationship from the master device to the previous tandem device, and a cascade networking hierarchy of the previous tandem device relative to the master device. And then, the last cascade device sends the return connection information of the last cascade device to the slave device, wherein the slave device is a next cascade device of the last cascade device.
And step S270, performing content replacement on the cascade networking connection information stored in the slave device by using the received return connection information.
In this embodiment, after a certain slave device receives the backhaul connection information sent by the currently connected previous tandem device, the received backhaul connection information is regarded as the cascade networking connection information of the slave device and stored, that is, the received backhaul connection information is used to directly replace the originally stored cascade networking connection information for storage.
Therefore, by executing the steps S260 and S270, the device routing status of the cascade devices to be connected, which is stored in each slave device, is updated in time when the MESH routing system completes networking, and the wireless networking result of the MESH routing system is solidified in time, so that the stability of the reorganization network of the MESH routing system is improved.
Optionally, referring to fig. 5, fig. 5 is a fourth flowchart illustrating a device networking method according to an embodiment of the present application. In this embodiment, compared with the device networking method shown in fig. 2, 3 or 4, the device networking method shown in fig. 5 may further include step S280 and step S290, where the step S280 and step S290 are used to update the device routing status of the next cascade device of the corresponding slave device in time when the MESH routing system completes networking, and to fix the wireless networking result of the MESH routing system in time, so as to improve the stability of the network reconfiguration of the MESH routing system.
Step S280, generating backhaul connection information for the slave device on the basis of the cascade networking connection information stored in the slave device, where the backhaul connection information records a second cascade relationship from the master device to the slave device, and a cascade networking hierarchy of the slave device relative to the master device.
In this embodiment, when a certain slave device successfully establishes a networking connection with a next-level networking device, the slave device adds identity information of the slave device to the end of a cascade routing relationship in the cascade networking connection information based on cascade networking connection information already determined by the slave device, so as to obtain a second cascade relationship from the master device to the slave device, and replaces a cascade networking hierarchy of a corresponding end cascade device in the cascade networking connection information with respect to the master device by using a cascade networking hierarchy of the slave device with respect to the master device, so as to obtain backhaul connection information of the slave device.
Step S290, the returned connection information of the slave device is sent to the next cascade device currently connected to the slave device, and the next cascade device is used as the cascade networking connection information of the next cascade device for storage.
In this embodiment, after the slave device determines its own backhaul connection information, it sends its own backhaul connection information to the next tandem device to which the slave device is currently connected, so that the next tandem device to which the slave device is currently connected stores the received backhaul connection information as the cascade networking connection information of the next tandem device.
Therefore, by executing the steps S280 and S290, when the MESH routing system completes networking, the present application may update the device routing status of the MESH routing system to the next cascade device corresponding to the slave device in time, and may solidify the wireless networking result of the MESH routing system in time, so as to improve the stability of the reorganization network of the MESH routing system.
In the present application, in order to ensure that the terminal device 10 can execute the device networking method through the device networking apparatus 100 when serving as a slave device, the foregoing functions are implemented by dividing functional modules of the device networking apparatus 100. The following describes specific components of the device networking apparatus 100 provided in the present application.
Referring to fig. 6, fig. 6 is a schematic diagram illustrating a component of the device networking apparatus 100 according to an embodiment of the present disclosure. In this embodiment, the device networking apparatus 100 may include a cascade information reading module 110, a connecting device selecting module 120, and a networking connection establishing module 130.
The cascade information reading module 110 is configured to read cascade networking connection information stored in the slave device, where the cascade networking connection information records a cascade routing relationship from the master device to a corresponding end cascade device.
A connecting device selecting module 120, configured to select a terminal cascade device corresponding to the cascade routing relationship as the current cascade device to be connected of the slave device.
A networking connection establishing module 130, configured to establish networking connection with the to-be-connected cascade device within a time period corresponding to a preset time duration.
Optionally, referring to fig. 7, fig. 7 is a second schematic view illustrating a composition of the device networking apparatus 100 according to the embodiment of the present application. In this embodiment of the present application, the cascade networking connection information further records a cascade networking hierarchy of the corresponding end cascade device relative to the master device, and the device networking apparatus 100 may further include a cascade relationship generation module 140.
The cascade relationship generating module 140 is configured to, in a time period corresponding to a preset time length, fail to establish networking connection with the cascade device to be connected, and remove the cascade device to be connected in the cascade routing relationship when the cascade networking hierarchy in the cascade networking connection information is not empty, so as to obtain a corresponding first cascade relationship.
The networking connection establishing module 130 is further configured to select each cascade device in reverse order according to the device cascade order of the first cascade relationship, and establish networking connection with the selected cascade device in a time period corresponding to a preset time length in sequence for the selected single cascade device until networking connection with a certain cascade device is successfully established.
Optionally, please refer to fig. 8, where fig. 8 is a third schematic diagram of a composition of the device networking apparatus 100 according to the embodiment of the present application. In this embodiment, the device networking apparatus 100 may further include a backhaul connection receiving module 150 and a concatenation information replacing module 160.
A backhaul connection receiving module 150, configured to receive backhaul connection information from a superior tandem device to which the slave device is currently connected.
And the cascade information replacement module 160 is configured to perform content replacement on the cascade networking connection information stored in the slave device by using the received backhaul connection information.
Optionally, please refer to fig. 9, where fig. 9 is a fourth schematic diagram illustrating a composition of the device networking apparatus 100 according to an embodiment of the present application. In this embodiment, the device networking apparatus 100 may further include a backhaul connection generating module 170 and a backhaul connection sending module 180.
A backhaul connection generating module 170, configured to generate backhaul connection information for the slave device on the basis of the cascade networking connection information stored in the slave device, where the backhaul connection information records a second cascade relationship from the master device to the slave device, and a cascade networking hierarchy of the slave device relative to the master device.
A backhaul connection sending module 180, configured to send backhaul connection information of the slave device to a next tandem device currently connected to the slave device, where the backhaul connection information is stored as cascade networking connection information of the next tandem device.
It should be noted that the basic principle and the technical effect of the device networking apparatus 100 provided in the embodiment of the present application are the same as those of the device networking method described above. For a brief description, the present embodiment is not mentioned in part, and reference may be made to the above description of the device networking method.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part. The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a readable storage medium, which includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned readable storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
In summary, in the device networking method and apparatus, the terminal device and the readable storage medium provided by the present application, the application aims at each slave end device in the MESH routing system, reads the cascade networking connection information stored by the slave end device, based on the cascade networking connection information record, selecting the cascade end equipment corresponding to the cascade route relation as the current cascade equipment to be connected of the slave end equipment, then establishing networking connection with corresponding cascade equipment to be connected in a time period corresponding to the preset time length, therefore, each slave end device in the same MESH routing system can carry out networking according to a specific device routing relation, wireless networking operation with strong routing condition stability is realized, and the influence of network fluctuation on a wireless networking result is reduced.
The above description is only for various embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the present application, and all such changes or substitutions are included in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A device networking method is applied to each slave end device included in a MESH routing system, wherein the MESH routing system further includes a master end device, and the method comprises the following steps:
reading cascade networking connection information stored in the slave end equipment, wherein the cascade networking connection information records a cascade routing relation from the master end equipment to corresponding tail end cascade equipment;
selecting the terminal cascade equipment corresponding to the cascade routing relation as the current cascade equipment to be connected of the slave end equipment;
and establishing networking connection with the cascade equipment to be connected within a time period corresponding to the preset time length.
2. The method according to claim 1, wherein the tandem networking connection information further records a tandem networking hierarchy of the corresponding end tandem device relative to the master device, and the method further comprises:
the method comprises the steps that networking connection cannot be established with the cascade equipment to be connected within a time period corresponding to preset time length, and the cascade equipment to be connected is removed from the cascade routing relation under the condition that the cascade networking hierarchy in cascade networking connection information is not empty, so that a corresponding first cascade relation is obtained;
and selecting all cascade equipment in a reverse order according to the equipment cascade sequence of the first cascade relation, and establishing networking connection with the cascade equipment in a time period corresponding to a preset time length aiming at the selected single cascade equipment in sequence until the networking connection with certain cascade equipment is successfully established.
3. The method of claim 2, further comprising:
receiving return connection information from the last cascade equipment currently connected with the slave end equipment;
and performing content replacement on the cascade networking connection information stored in the slave end equipment by adopting the received return connection information.
4. The method according to any one of claims 1-3, further comprising:
generating backhaul connection information for the slave end device on the basis of the cascade networking connection information stored by the slave end device, wherein the backhaul connection information records a second cascade relationship from the master end device to the slave end device and a cascade networking hierarchy of the slave end device relative to the master end device;
and sending the returned connection information of the slave end equipment to the next cascade equipment currently connected with the slave end equipment as the cascade networking connection information of the next cascade equipment for storage.
5. An apparatus networking device, which is applied to each slave device included in a MESH routing system, wherein the MESH routing system further includes a master device, the apparatus further includes:
the cascade information reading module is used for reading cascade networking connection information stored in the slave end equipment, wherein the cascade networking connection information records a cascade routing relation from the master end equipment to the corresponding tail end cascade equipment;
a connection device selection module, configured to select a terminal cascade device corresponding to the cascade routing relationship as a current cascade device to be connected to the slave device;
and the networking connection establishing module is used for establishing networking connection with the cascade equipment to be connected within a time period corresponding to the preset time length.
6. The apparatus according to claim 5, wherein the tandem networking connection information further records a tandem networking hierarchy of the corresponding end tandem device relative to the master device, and the apparatus further comprises:
the cascade connection relation generating module is used for removing the cascade equipment to be connected in the cascade routing relation under the condition that the cascade networking connection with the cascade equipment to be connected cannot be established within the time period corresponding to the preset time length and the cascade equipment to be connected is not empty in the cascade networking connection information, so as to obtain a corresponding first cascade relation;
and the networking connection establishing module is further used for selecting all the cascade equipment in reverse order according to the equipment cascade sequence of the first cascade relation, and establishing networking connection with the cascade equipment in a time period corresponding to the preset time length aiming at the selected single cascade equipment in sequence until the networking connection with certain cascade equipment is successfully established.
7. The apparatus of claim 6, further comprising:
a backhaul connection receiving module, configured to receive backhaul connection information from a previous tandem device to which the slave device is currently connected;
and the cascade information replacement module is used for performing content replacement on the cascade networking connection information stored in the slave equipment by adopting the received returned connection information.
8. The apparatus of any one of claims 5-7, further comprising:
a backhaul connection generation module, configured to generate backhaul connection information for the slave device on the basis of the cascade networking connection information stored in the slave device, where the backhaul connection information records a second cascade relationship from the master device to the slave device, and a cascade networking hierarchy of the slave device relative to the master device;
and the return connection sending module is used for sending the return connection information of the slave end equipment to the next cascade equipment currently connected with the slave end equipment as the cascade networking connection information of the next cascade equipment for storage.
9. A terminal device, configured to act as a slave device other than a master device included in a MESH routing system, the terminal device comprising a processor and a memory, wherein the memory stores a computer program executable by the processor, and the processor executes the computer program to implement the device networking method according to any one of claims 1 to 4.
10. A readable storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the device networking method of any one of claims 1-4.
CN202111199735.8A 2021-10-14 2021-10-14 Equipment networking method and device, terminal equipment and readable storage medium Pending CN113950120A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111199735.8A CN113950120A (en) 2021-10-14 2021-10-14 Equipment networking method and device, terminal equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111199735.8A CN113950120A (en) 2021-10-14 2021-10-14 Equipment networking method and device, terminal equipment and readable storage medium

Publications (1)

Publication Number Publication Date
CN113950120A true CN113950120A (en) 2022-01-18

Family

ID=79329922

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111199735.8A Pending CN113950120A (en) 2021-10-14 2021-10-14 Equipment networking method and device, terminal equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN113950120A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023241566A1 (en) * 2022-06-16 2023-12-21 华为技术有限公司 Networking method and system, and related apparatus

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110235504A1 (en) * 2010-03-26 2011-09-29 Oki Electric Industry Co., Ltd. Wireless communication system and nodes
CN106878969A (en) * 2017-01-04 2017-06-20 普联技术有限公司 Wireless networking method, wireless networking devices and system
CN108848498A (en) * 2018-06-22 2018-11-20 北京格瑞空间科技有限公司 A kind of netted self-organized network communication system and method based on LoRa
WO2019237262A1 (en) * 2018-06-13 2019-12-19 卧槽科技(深圳)有限公司 Low-power bluetooth networking method, electronic device, network, and storage medium
CN112954721A (en) * 2019-11-26 2021-06-11 中兴通讯股份有限公司 Back transmission method and unit, data distribution method and controller, network system and medium

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110235504A1 (en) * 2010-03-26 2011-09-29 Oki Electric Industry Co., Ltd. Wireless communication system and nodes
CN106878969A (en) * 2017-01-04 2017-06-20 普联技术有限公司 Wireless networking method, wireless networking devices and system
WO2019237262A1 (en) * 2018-06-13 2019-12-19 卧槽科技(深圳)有限公司 Low-power bluetooth networking method, electronic device, network, and storage medium
CN108848498A (en) * 2018-06-22 2018-11-20 北京格瑞空间科技有限公司 A kind of netted self-organized network communication system and method based on LoRa
CN112954721A (en) * 2019-11-26 2021-06-11 中兴通讯股份有限公司 Back transmission method and unit, data distribution method and controller, network system and medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023241566A1 (en) * 2022-06-16 2023-12-21 华为技术有限公司 Networking method and system, and related apparatus

Similar Documents

Publication Publication Date Title
CN110288345B (en) Cross-link communication method, device, main chain node and storage medium
CN107332876B (en) Method and device for synchronizing block chain state
EP3605323B1 (en) Method for generating network slice template and for applying network slice template, and apparatus
CN108667727B (en) Network link fault processing method and device and controller
JP2019518257A (en) State control method and apparatus
CN108712491A (en) Block chain node, exchange information processing method, terminal device and medium
CN106331152B (en) Method and device for realizing information synchronization between modules
CN111654399B (en) Networking method, device, equipment and storage medium based on SD-WAN
CN104301141A (en) Method, device and system for storing configuration information
CN112702167B (en) Cluster feature code obtaining method and device and electronic equipment
CN108737105A (en) Method for retrieving, device, private key equipment and the medium of private key
CN112911671A (en) Method and device for constructing topology networking architecture
CN113950120A (en) Equipment networking method and device, terminal equipment and readable storage medium
CN107678804B (en) Behavior execution method and apparatus, storage medium, and electronic apparatus
CN110602732B (en) Wireless configuration parameter synchronization method, device, network equipment and computer readable storage medium
CN110311826B (en) Network equipment configuration method and device
CN111800491A (en) Data transmission method, system, computing device and storage medium
CN101674251B (en) Method for upgrade processing for recursive router, device and router therefor
CN114882628B (en) Data processing method and device, electronic equipment and computer readable medium
CN112688870B (en) Routing method, routing device and node equipment
CN113346974B (en) Method, apparatus, communication system and storage medium for clock synchronization
CN115269056A (en) Encryption module plug-in method and device based on class loader and related product
CN112256658B (en) Log record distribution method and device, storage medium and electronic device
CN114785800A (en) Cross-link communication method and device
CN109194613B (en) Data packet detection method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination