A kolink lightweight wireless networking management method for cluster management

Abstract

This invention discloses a Kolink lightweight wireless networking management method for cluster management, relating to the field of wireless networking technology. It includes a gateway, a gateway repeater, nodes, and a management platform. The gateway is used for wireless networking and data transmission with the gateway repeater and nodes. The gateway and management platform interact with each other for service data. The gateway repeater is used for data forwarding between the gateway and nodes. When the distance between the gateway and nodes is long, data forwarding can be achieved by adding more gateway repeaters. The advantages of this invention are: nodes and gateways can quickly form a network using the Kolink lightweight wireless networking method; nodes can interact with each other through the gateway and management platform; for nodes where networking is impossible due to long distances, gateway repeaters can be added between the gateway and nodes, with a maximum of two levels of gateway repeaters. It consumes few hardware resources, increases hardware costs slightly, and offers flexible networking options, including probe-based networking and designated node joining.

Description

Technical Field

[0001] This invention relates to the field of wireless networking technology, specifically to a Kolink lightweight wireless networking management method for trunking management. Background Technology

[0002] With the popularization of IoT technology, communication between devices is becoming more frequent. Devices establish connections through wireless communication and then access the cloud control platform through gateway devices, allowing users to access and control devices anytime and anywhere through IoT, making device control and management more convenient and intelligent.

[0003] The existing technology has the following drawbacks:

[0004] 1. To connect to the management platform using Wi-Fi or Ethernet cable, you need to lay the cables in advance, prepare a router or switch, and ensure the gateway is connected to the Internet. Alternatively, you can use a cellular 2G / 3G / 4G / 5G wireless module to connect to the management platform. Device networking requires a dedicated networking module, which significantly increases equipment costs. The wireless networking module also requires an IoT card, which will incur data usage fees, adding to the overall expense.

[0005] 2. A networking module is installed on the gateway, and nodes connect to the gateway. Data is forwarded through the gateway and communicates with the management platform. Communication between nodes and the gateway uses wired transmission, such as RS485, CAN, RS232, etc., which requires separate laying of communication cables, increasing material and construction costs, resulting in high maintenance costs and potential failures of the entire line of equipment due to line faults.

[0006] Using only wireless modules for transparent transmission can lead to data conflicts, channel interference, and network failures. Hardware based on protocols such as LoRaWAN, Bluetooth, and Zigbee is very expensive, the protocols are complex and consume a lot of hardware resources, the networking methods are limited, and nodes cannot be upgraded over-the-air (OTA). For node upgrades and function updates, the only option is to burn the program on-site.

[0007] In summary, a lightweight Kolink wireless networking method for cluster management has been developed. Summary of the Invention

[0008] (a) Technical problems to be solved

[0009] To address the shortcomings of existing technologies, this invention provides a lightweight Kolink wireless network management method for cluster management, which has advantages such as low power consumption, low cost, and good scalability, and solves the problems of high cost, high power consumption, and limited network configuration.

[0010] (II) Technical Solution

[0011] To achieve the above objectives, this invention provides the following technical solution: a Kolink lightweight wireless networking management method for cluster management, comprising a gateway, a gateway repeater, nodes, and a management platform. The gateway is used for wireless networking and data transmission with the gateway repeater and nodes. The gateway and management platform interact with each other for service data. The gateway repeater is used for data forwarding between the gateway and nodes. The nodes are used for data interaction and networking with the gateway and gateway repeater. When the distance between the gateway and nodes is too far to form a network, data forwarding can be achieved by adding more gateway repeaters. The gateway repeater and gateway are used in a bound manner, eliminating the need for... The network enables data forwarding between gateways and nodes, with a maximum of two cascaded levels. The first level supports a maximum of [number] gateway repeaters, and the second level supports a maximum of [number] gateway repeaters. Nodes are terminal devices, directly used by users. Human-computer interaction and user operation involve communication between nodes and gateways, either via gateway repeaters or directly. Gateways interact with the management platform for business data exchange. Each node has a unique ID. The management platform interacts with the gateway for business data exchange and provides backend management for node usage. The gateway and node network includes two forms: probe-based networking and designated node joining. Probe-based networking includes the following steps:

[0012] S1: The gateway enters the network detection state;

[0013] S2: The node is in the waiting state to join the network, working on the default channel and at the default rate. In this state, it can receive broadcast networking commands sent by the node gateway.

[0014] S3: The gateway sends a network detection command;

[0015] S4: Random delay occurs when the node receives the network configuration command;

[0016] S5: The gateway enters data receiving mode, starts a 10-second timeout timer, and waits to receive network access information from the specified node. If no network access information is received after the timeout, it proceeds to S14.

[0017] S6: After the node executes S4 and ends the delay, it sends the network entry information data. After sending, it switches to data receiving mode.

[0018] S7: The gateway receives the network entry information data sent by node S6 via S5. After a 10-second delay, it selects the node that best meets the network entry conditions and determines whether to allow network entry. If the network entry conditions are met, it proceeds to S8; otherwise, it proceeds to S14.

[0019] S8: The gateway sends broadcast data, broadcasting network parameters (including but not limited to working channel, working speed, network access node ID, silence time of other devices, etc.);

[0020] S9: The node waits to receive the network access permission instruction. If the network parameter information received from the gateway is not the node's ID, it enters S10. If the network parameter information received from the gateway is the node's ID, it enters S11.

[0021] S10: The node enters the network access waiting state;

[0022] S11: The node switches to the working channel and working rate in the network parameter information and waits for the gateway to send a handshake command.

[0023] S12: The gateway switches to the working channel and rate, sends a handshake command, and waits for the node to respond to the handshake command.

[0024] S13: After the node and gateway complete the network formation through three handshake commands, the network formation information is saved, the network formation ends, and the node enters the working state.

[0025] S14: After waiting for the handshake command in S12 for a timeout, the system re-enters the next detection network cycle;

[0026] S15: Save network information. If the gateway network setup time expires, the maximum number of supported networks is reached, or the gateway network is manually exited, proceed to S16; otherwise, proceed to S1 and enter the next network detection loop.

[0027] S16: End this network setup and enter working state;

[0028] The process of designating a node to join the network includes the following steps:

[0029] Step 1: When the gateway is working normally, it receives a network access instruction for a specified node from the management platform.

[0030] Step 2: The gateway switches to the specified channel and sends the network configuration command for the specified node at the specified rate. After sending, proceed to Step 3.

[0031] Step 3: The gateway enters data receiving mode, starts a 10-second timeout timer, and waits to receive the network entry information from the specified node. If no network entry information is received after the timeout, proceed to step 12.

[0032] Step 4: After receiving the designated node networking instruction sent by the gateway in Step 2, the node proceeds to Step 5;

[0033] Step 5: The node sends network access information data to the gateway, and enters the data receiving state after sending is complete;

[0034] Step 6: The gateway receives the network access information from the node, determines whether to allow network access, and if the network access conditions are met, proceeds to Step 7; if the network access conditions are not met, proceeds to Step 12.

[0035] Step 7: The gateway sends broadcast data, broadcasting network parameters;

[0036] Step 8: The node waits to receive the network access permission instruction. When it receives the network parameter information sent by the gateway and finds that it has the 3ID of this node, it proceeds to step 10.

[0037] Step 9: The gateway switches to the working channel and rate and sends a handshake command, waits for the device to respond to the handshake command, and waits for the handshake command to time out before proceeding to step 12;

[0038] Step 10: The node switches to the specified channel and rate, waits for the gateway to send a handshake command, and proceeds to step 11 if the handshake is successful;

[0039] Step 11: Save network information, end network setup, enter working state, and proceed to Step 13;

[0040] Step 12: Wait for timeout, retry, if the number of retries is reached, the network is considered to have failed and proceed to Step 13;

[0041] Step 13: End the network setup, save the newly added network parameters, and switch to the normal operating channel rate.

[0042] Preferably, in both of the aforementioned networking forms, the gateway repeater serves as a data forwarder between the gateway and the nodes during the networking process. Without networking, the number of nodes that a single gateway can network can be modified, with a modification range of 1-128 nodes.

[0043] Preferably, in the designated node network access mode, when the gateway is working normally, it receives the designated node network access instruction issued by the management platform to the gateway.

[0044] Preferably, in the designated node network entry method, a designated node network entry instruction is sent according to the channel, rate, and node ID issued by the management platform to complete the network formation of the designated ID node. This network formation method is independent of whether the node has already been networked.

[0045] Preferably, the management platform sends the node OTA firmware to the gateway, the gateway stores the node OTA firmware, and file transfer can be achieved through the networking protocol. The gateway sends the OTA firmware to the node, and after the node receives the firmware, it verifies the data integrity. If the verification is successful, it updates its own firmware.

[0046] (III) Beneficial Effects

[0047] Compared with existing technologies, this invention provides a lightweight Kolink wireless network management method for cluster management, which has the following advantages:

[0048] This Kolink lightweight wireless networking management method for cluster management enables nodes and gateways to quickly form a network. Nodes can interact with the gateway and management platform. For nodes that are too far apart to form a network, a gateway repeater can be added between the gateway and the node. Up to two gateway repeaters can be added. It consumes few hardware resources and increases hardware costs only slightly. The networking is flexible and can be divided into detection networking and designated node joining.

[0049] This Kolink lightweight wireless networking management method for cluster management allows data transmission in areas with poor network signal. Simply place the gateway in a location with good signal, and the nodes and gateway will form a network. If wireless signal coverage is insufficient, a gateway repeater can be added to increase the networking distance between the gateway and nodes. It offers good scalability and flexibility. 4. Nodes can be upgraded remotely via OTA. Attached Figure Description

[0050] Figure 1 This is a schematic diagram of the Kolink lightweight wireless networking method for cluster management proposed in this invention;

[0051] Figure 2 This is a schematic diagram of the detection network process proposed in this invention;

[0052] Figure 3 This is a schematic diagram of the designated node network access process proposed in this invention.

[0053] In the diagram: 1-Gateway, 2-Gateway Repeater, 3-Node, 4-Management Platform. Detailed Implementation

[0054] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0055] Please see Figure 1-3A lightweight Kolink wireless networking management method for cluster management includes a gateway 1, a gateway repeater 2, nodes 3, and a management platform 4. Gateway 1 is used for wireless networking and data transmission with gateway repeater 2 and nodes 3. Gateway 1 and the management platform 4 interact with each other for service data. Gateway repeater 2 is used for data forwarding between gateway 1 and nodes 3. Node 3 is used for data interaction and networking with gateway 1 and gateway repeater 2. When gateway 1 and nodes 3 are too far apart to form a network, gateway repeater 2 can be added to achieve data forwarding. Gateway repeater 2 and gateway 1 are used together without the need for network formation, thus realizing gateway... Data forwarding between Node 1 and Node 3 can be cascaded up to two levels. The first level supports up to 5 Gateway Repeaters 2, and the second level supports up to 3 Gateway Repeaters 2. Node 3 is the terminal device, the direct device used by the user. The human-machine interaction process and user operation involve the node communicating with Gateway 1 via Gateway Repeater 2 or directly. Gateway 1 interacts with the management platform 4 for business data. Each node has a unique ID. The management platform 4 is used for business data interaction with Gateway 1 and for the background management of Node 3. The networking of Gateway 1 and Node 3 includes two networking forms: probe networking and designated node joining. Probe networking includes the following steps:

[0056] S1: Gateway 1 enters the network detection state;

[0057] S2: Node 3 is in the waiting state to join the network, working on the default channel and at the default rate. In this state, it can receive broadcast networking commands sent by the Node 3 gateway.

[0058] S3: Gateway 1 sends a network detection command;

[0059] S4: Node 3 receives the network formation command and experiences a random delay;

[0060] S5: Gateway 1 enters data receiving mode, starts a 10-second timeout timer, and waits to receive the network entry information from the designated node 3. If the network entry information is not received after the timeout, proceed to S14.

[0061] S6: After node 3 executes S4 and ends the delay, it sends the network entry information data. After sending, it switches to data receiving mode.

[0062] S7: Gateway 1 receives the network entry information data sent by node 3 in S6 via S5. After a 10-second delay, it selects the node that best meets the network entry conditions and determines whether to allow network entry. If the network entry conditions are met, it proceeds to S8; otherwise, it proceeds to S14.

[0063] S8: Gateway 1 sends broadcast data, broadcasting network parameters (including but not limited to working channel, working speed, network access node ID, silence time of other devices, etc.);

[0064] S9: Node 3 waits to receive the network access permission instruction. If the network parameter information received from gateway 1 is not the ID of this node 3, it enters S10. If the network parameter information received from gateway 1 is the ID of this node 3, it enters S11.

[0065] S10: Node 3 enters the network access waiting state;

[0066] S11: Node 3 switches to the working channel and working rate in the network parameter information and waits for gateway 1 to send a handshake command;

[0067] S12: Gateway 1 switches to the working channel and rate, sends a handshake command, and waits for node 3 to respond to the handshake command.

[0068] S13: After three handshake commands, Node 3 and Gateway 1 complete the network formation, save the network information, end the network formation, and enter the working state.

[0069] S14: After waiting for the handshake command in S12 for a timeout, the system re-enters the next detection network cycle;

[0070] S15: Save network information. If the network setup time of Gateway 1 expires, the maximum number of supported networks is reached, or the gateway network is manually exited, proceed to S16; otherwise, proceed to S1 and enter the next network detection loop.

[0071] S16: End this network setup and enter working state;

[0072] The process of designating a node to join the network includes the following steps:

[0073] Step 1: When Gateway 1 is working normally, it receives a network access instruction for a designated node from the management platform 4.

[0074] Step 2: Gateway 1 switches to the specified channel and sends the specified node networking command at the specified rate. After sending, proceed to Step 3.

[0075] Step 3: Gateway 1 enters data receiving mode, starts a 10-second timeout timer, and waits to receive the network entry information from the designated node 3. If the network entry information is not received after the timeout, proceed to step 12.

[0076] Step 4: After receiving the designated node networking instruction sent by gateway 1 in Step 2, node 3 proceeds to Step 5;

[0077] Step 5: Node 3 sends network access information data to gateway 1, and enters the data receiving state after sending is complete;

[0078] Step 6: Gateway 1 receives the network access information from Node 3, determines whether network access is allowed, and proceeds to Step 7 if network access is allowed; otherwise, proceeds to Step 12.

[0079] Step 7: Gateway 1 sends broadcast data, broadcasting network parameters;

[0080] Step 8: Node 3 waits to receive the network access permission instruction. When it receives the network parameter information sent by gateway 1 and finds that it is the ID of this node 3, it proceeds to step 10.

[0081] Step 9: Gateway 1 switches to the working channel and rate and sends a handshake command, waits for Node 3 to respond to the handshake command, and waits for the handshake command to time out before proceeding to Step 12;

[0082] Step 10: Node 3 switches to the specified channel and rate, waits for Gateway 1 to send a handshake command, and proceeds to Step 11 if the handshake is successful;

[0083] Step 11: Save network information, end network setup, enter working state, and proceed to Step 13;

[0084] Step 12: Wait for timeout, retry, if the number of retries is reached, the network is considered to have failed and proceed to Step 13;

[0085] Step 13: End the network setup, save the newly added network parameters in Gateway 1, and switch to the normal operating channel rate.

[0086] Preferably, in both networking configurations, the gateway repeater 2 serves as a data forwarder between the gateway 1 and the node 3 during the networking process. Without networking, the number of nodes 3 that can be networked by one gateway 1 can be modified, with a modification range of 1-128 nodes.

[0087] When gateway 1 is working normally in the designated node network access mode, it receives the designated node network access instruction issued by management platform 4 to gateway 1.

[0088] In the designated node network entry method, according to the channel, rate, and node ID issued by the management platform 4, a designated node network entry command is sent to complete the network formation of node 3 with the designated ID. This network formation method is independent of whether node 3 has already been networked.

[0089] The management platform 4 sends the OTA firmware of node 3 to gateway 1. Gateway 1 saves the OTA firmware of node 3. File transfer can be achieved through the networking protocol. Gateway 1 sends the OTA firmware to node 3. After receiving the firmware, node 3 verifies the data integrity. If the verification is successful, it updates its own firmware.

[0090] In summary, this Kolink lightweight wireless networking management method for cluster management enables node 3 and gateway 1 to quickly form a network. Node 3 can interact with the management platform 4 through gateway 1. For nodes where gateway 1 and node 3 are too far apart to form a network, a gateway repeater 2 can be added between gateway 1 and node 3. Up to two levels of gateway repeaters can be added. This method consumes minimal hardware resources and increases hardware costs only slightly. The networking is flexible and can be divided into detection networking and designated node joining.

[0091] This Kolink lightweight wireless networking management method for cluster management allows for data transmission in areas with poor network signal. Simply place gateway 1 in a location with good signal, and node 3 and gateway 1 will form a network. If wireless signal coverage is insufficient, gateway repeater 2 can be added to increase the networking distance between node 1 and node 3. It offers good scalability and flexibility. 4. Nodes can be upgraded remotely via OTA.

[0092] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0093] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A lightweight Kolink wireless network management method for cluster management, characterized in that: The system includes a gateway (1), a gateway repeater (2), nodes (3), and a management platform (4). The gateway (1) is used for wireless networking and data transmission with the gateway repeater (2) and nodes (3). The gateway repeater (2) is used for data forwarding between the gateway (1) and nodes (3). The nodes (3) are charging piles. The management platform (4) is used for business data interaction with the gateway (1) and for the background management of the nodes (3). The networking of the gateway (1) and nodes (3) includes two networking forms: probe networking and designated node network entry. The probe networking includes the following steps: S1: Gateway (1) enters the detection network state; S2: Node (3) is in the waiting state for network entry, working in the default channel and default rate. In this state, it can receive broadcast network entry commands sent by the gateway of node (3). S3: Gateway (1) sends a network detection command; S4: Node (3) receives the networking command and generates a random delay; S5: Gateway (1) enters data receiving mode, starts a 10-second timeout timer, waits to receive network access information from the designated node (3), and enters S14 if no network access information is received after the timeout. S6: After node (3) executes S4, it ends the delay and then sends the network entry information data. After sending, it switches to data receiving mode. S7: The gateway (1) receives the network entry information data sent by node (3) of S6 via S5. After a 10-second delay, it selects the node that best meets the network entry conditions and determines whether to allow network entry. If the network entry conditions are met, it proceeds to S8; otherwise, it proceeds to S14. S8: Gateway (1) sends broadcast data, broadcasting network parameters; S9: Node (3) waits to receive the network access permission instruction. When the network parameter information sent by the gateway (1) is not the ID of this node (3), it enters S10. When the network parameter information sent by the gateway (1) is the ID of this node (3), it enters S11. S10: Node (3) enters the network access state; S11: Node (3) switches to the working channel working rate in the network parameter information and waits for the gateway (1) to send a handshake instruction; S12: Gateway (1) switches to working channel and rate, sends handshake command, and waits for node (3) to respond to handshake command; S13: After three handshake commands, node (3) and gateway (1) complete the network formation, save the network information, end the network formation, and enter the working state. S14: After waiting for the handshake command in S12 for a timeout, the system re-enters the next detection network cycle; S15: Save network information. After the gateway (1) network timeout, network reaches the maximum supported number, or the gateway exits the network manually, proceed to S16; otherwise, proceed to S1 and enter the next network detection loop. S16: End this network setup and enter working state; The process of designating a node to join the network includes the following steps: Step 1: When the gateway (1) is working normally, it receives the network access instruction for the specified node issued by the management platform (4) to the gateway (1). Step 2: Gateway (1), switch to the specified channel and send the specified node networking command at the specified rate. After sending, proceed to step 3. Step 3: The gateway (1) enters the data receiving mode, starts a 10-second timeout timer, and waits to receive the network entry information of the designated node (3). If the network entry information is not received after the timeout, proceed to step 12. Step 4: After receiving the designated node networking instruction sent by the gateway (1) in Step 2, node (3) proceeds to Step 5; Step 5: Node (3) sends network access information data to gateway (1), and enters the data receiving state after sending is completed; Step 6: The gateway (1) receives the network access information from the node (3), determines whether network access is allowed, and proceeds to step 7 if the network access conditions are met; otherwise, it proceeds to step 12. Step 7: Gateway (1) sends broadcast data, broadcasting network parameters; Step 8: Node (3) waits to receive the network access permission instruction. When it receives the network parameter information sent by the gateway (1) and finds that it is the ID of this node (3), it proceeds to step 10. Step 9: The gateway (1) switches to the working channel and rate to send a handshake command, waits for the node (3) to respond to the handshake command, and waits for the handshake command to time out before proceeding to step 12; Step 10: Node (3) switches to the specified channel and rate, waits for gateway (1) to send a handshake command, and proceeds to step 11 after a successful handshake. Step 11: Save network information, end network setup, enter working state, and proceed to Step 13; Step 12: Wait for timeout, retry, if the number of retries is reached, the network is considered to have failed and proceed to Step 13; Step 13: End the network formation, the gateway (1) saves the newly added network parameters and switches to the normal working channel rate.

2. The Kolink lightweight wireless network management method for cluster management according to claim 1, characterized in that: In both networking forms, the gateway repeater (2) plays the role of connecting the gateway (1) and the node (3) during the networking process, and allows the data between the two to be forwarded to each other. Without networking, the number of nodes that can be networked by one gateway (1) can be modified, with a modification range of 1-128 nodes.

3. The Kolink lightweight wireless network management method for cluster management according to claim 2, characterized in that: When the gateway (1) is working normally in the specified node network access mode, it receives the specified node network access instruction issued by the management platform (4) to the gateway (1).

4. The Kolink lightweight wireless network management method for cluster management according to claim 1, characterized in that: In the specified node network entry mode, according to the channel, rate and node ID issued by the management platform (4), a specified node network entry instruction is sent to complete the networking of the specified ID node (3).

5. The Kolink lightweight wireless network management method for cluster management according to claim 1, characterized in that: The management platform (4) sends the OTA firmware of node (3) to the gateway (1). The gateway (1) saves the OTA firmware of node (3). File transfer can be achieved through the networking protocol. The gateway (1) sends the OTA firmware to node (3). After receiving the firmware, node (3) verifies the data integrity. If the verification is successful, it updates its own firmware.

Images