Hybrid network architecture, method and system based on lora and mesh

Abstract

The application discloses a hybrid network architecture, method and system based on LORA and MESH, comprising: a plurality of hybrid network backbone nodes, the backbone node comprising a LoRa access end, a Mesh relay end and a channel management unit, the LoRa access end is configured to establish a star connection relationship with a plurality of user terminals in the access layer network by using a configurable channel frequency point in the same frequency band, the channel frequency points of the LoRa access ends of adjacent backbone nodes are different, the user terminal is configured to automatically roam and switch to the channel frequency point of the target backbone node according to the signal strength; the Mesh relay end is configured to communicate in the backbone layer network by using a single fixed frequency point, and establish a multi-hop mesh connection relationship with adjacent backbone nodes; the channel management unit is configured to establish a data direct channel by a pipeline communication protocol and connect the LoRa access end and the Mesh relay end. According to the application, the user terminal can be deployed in a lightweight manner, and the application scenarios are widened.

Description

Technical Field

[0001] This application relates to the field of communication technology, particularly to the field of networking technology, and especially to a hybrid network architecture, networking method and system based on LoRa and Mesh. Background Technology

[0002] With the advancement of the times and the continuous development of technology, the construction of smart cities has become an important direction, and the Internet of Things (IoT) technology provides the foundation for smart cities. Currently, among IoT technologies, LoRa has become a popular choice. Traditional LoRa networking uses a star topology, which, although simple in structure, low in cost, and with low latency, often requires manual intervention during networking and lacks relay routing, resulting in limited coverage and significantly restricting application scenarios.

[0003] Therefore, to expand coverage, related technologies combine Mesh networking with LoRa networking. Mesh networking is a network topology where each node can communicate directly with its neighbors, ultimately forming an interconnected mesh structure. Thus, in a LoRa-based Mesh networking scheme, each node in the mesh network can act as a relay router, increasing transmission distance, achieving fully automatic networking, and extending coverage through multi-hop relays.

[0004] However, in the LoRa-based Mesh networking schemes mentioned above, the terminal nodes require high power consumption, making them unsuitable for low-power devices powered by batteries, thus limiting their applicability. Summary of the Invention

[0005] In view of this, embodiments of this application provide a hybrid network architecture, networking method and system based on LoRa and MESH, which can reduce the power consumption of terminal nodes, realize lightweight deployment of user terminals and broaden the applicable scenarios.

[0006] In a first aspect, embodiments of this application provide a hybrid network architecture based on LoRa and Mesh, comprising: multiple hybrid network backbone nodes, each backbone node including a LoRa access terminal, a Mesh relay terminal, and a channel management unit, wherein: the LoRa access terminal is configured to establish a star-shaped connection with multiple user terminals using configurable channel frequencies within the same frequency band in the access layer network, wherein the channel frequencies of the LoRa access terminals of adjacent backbone nodes are different, and the user terminals are configured to automatically roam and switch to the channel frequency of the target backbone node based on signal strength to achieve roaming access across backbone nodes; the Mesh relay terminal is configured to use a single fixed frequency in the backbone layer network. It enables communication and establishes multi-hop mesh connections with adjacent backbone nodes. The channel management unit is configured to establish a direct data channel through a pipeline communication protocol and connect the LoRA access point and the Mesh relay point. It converts the data packets of the LoRA access point into Mesh protocol format in real time and converts the data packets of the Mesh relay point into LoRA protocol format in real time. The hybrid network architecture is deployed in groups of three backbone nodes. Multiple groups of units are extended through inter-group connection links to form a multi-layer topology network. The three LoRA access points in each group of units are configured with three different channel frequencies. Multiple groups of units within the same preset area reuse the three channel frequencies.

[0007] Secondly, embodiments of this application provide a networking method based on LoRa and Mesh, applied to the hybrid network architecture based on LoRa and Mesh as described in the first aspect. The hybrid network architecture includes multiple hybrid network backbone nodes, each backbone node comprising a LoRa access terminal, a Mesh relay terminal, and a channel management unit. The method includes: the LoRa access terminal establishing a star-shaped connection with multiple user terminals in the access layer network using configurable channel frequencies within the same frequency band, wherein the channel frequencies of the LoRa access terminals of adjacent backbone nodes are different, and the user terminals are configured to automatically roam and switch to the channel frequency of the target backbone node based on signal strength to achieve roaming access across backbone nodes; the Mesh relay terminal... The LoRA access point communicates using a single fixed frequency in the backbone network and establishes a multi-hop mesh connection with adjacent backbone nodes. The channel management unit establishes a direct data channel through the pipeline communication protocol and connects the LoRA access point and the Mesh relay point. It converts the data packets of the LoRA access point into Mesh protocol format in real time and converts the data packets of the Mesh relay point into LoRA protocol format in real time. The hybrid network architecture is deployed in groups of three backbone nodes. Multiple groups of units are extended through inter-group connection links to form a multi-layer topology network. The three LoRA access points in each group of units are configured with three different channel frequencies. Multiple groups of units within the same preset area reuse the three channel frequencies.

[0008] Thirdly, embodiments of this application provide a networking system based on LoRa and Mesh, comprising the hybrid network architecture based on LoRa and Mesh as described in the first aspect. The system includes: multiple hybrid network backbone nodes, each backbone node comprising a LoRa access terminal, a Mesh relay terminal, and a channel management unit, wherein: the LoRa access terminal is used to establish a star-shaped connection with multiple user terminals in the access layer network using configurable channel frequencies within the same frequency band, wherein the channel frequencies of the LoRa access terminals of adjacent backbone nodes are different, and the user terminals are configured to automatically roam and switch to the channel frequency of the target backbone node based on signal strength to achieve roaming access across backbone nodes; the Mesh relay terminal is used to establish a star-shaped connection with multiple user terminals in the access layer network using configurable channel frequencies within the same frequency band. The backbone network uses a single fixed frequency for communication and establishes multi-hop mesh connections with adjacent backbone nodes. The channel management unit is used to establish a direct data channel through the pipeline communication protocol and connect the LoRA access terminal and the Mesh relay terminal. It converts the data packets of the LoRA access terminal into Mesh protocol format in real time and converts the data packets of the Mesh relay terminal into LoRA protocol format in real time. The hybrid network architecture is deployed in groups of three backbone nodes. Multiple groups of units are extended through inter-group connection links to form a multi-layer topology network. The three LoRA access terminals in each group of units are configured with three different channel frequencies. Multiple groups of units within the same preset area reuse the three channel frequencies.

[0009] This application provides a hybrid network architecture, networking method, and system based on LoRa and Mesh. It combines Mesh self-organizing networks with LoRa central networking to form a novel wireless communication network architecture that integrates lines, planes, and areas. Specifically, it fully leverages the wireless extension characteristics of Mesh self-organizing networks as the backbone network for lines and planes, while utilizing the advantages of LoRa—low cost, low power consumption, light weight, small size, and long operating time—to enable large-scale deployment of user terminals. Furthermore, in this hybrid network structure, the Mesh relays of the backbone nodes fully undertake routing functions and maintain the backbone topology. The channel management unit of the backbone nodes shields the terminals from awareness of the Mesh protocol through protocol conversion. Based on this, user terminals only establish a star connection with the LoRa access points of the backbone nodes and only need to listen to the channel information of the LoRa access points, without participating in the multi-hop routing of the Mesh relays, thus eliminating the energy burden of data relay. Meanwhile, the hybrid network architecture deploys in groups of three backbone nodes, with each backbone node using a different channel to avoid co-channel interference between adjacent nodes. Frequency reuse between groups effectively improves spectrum utilization and supports massive terminal access. Multiple groups can be extended through inter-group links to form a multi-layered topology network. Thus, this hybrid network structure can achieve large-area, long-distance wireless network coverage while simultaneously enabling lightweight user terminals, reducing deployment and usage costs, and allowing for unlimited deployment numbers, effectively broadening its applicability. Attached Figure Description

[0010] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings of the embodiments of this application will be briefly described below.

[0011] Figure 1 This is an exemplary schematic diagram of a hybrid network architecture based on LoRa and Mesh provided in an embodiment of this application; Figure 2 This is an exemplary schematic diagram of a group unit in a hybrid network structure provided in an embodiment of this application; Figure 3 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0012] The principles and spirit of this application will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided to make the principles and spirit of this application clearer and more thorough, enabling those skilled in the art to better understand and implement the principles and spirit of this application. The exemplary embodiments provided herein are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments described herein without inventive effort are within the scope of protection of this application.

[0013] In this document, terms such as first, second, and third are used only to distinguish one entity (or operation) from another entity (or operation), and are not intended to require or imply any order or relationship between these entities (or operations).

[0014] The applicant's research revealed that traditional LoRa-based Mesh networking solutions have at least the following drawbacks: Mesh networking requires terminal nodes to participate in data forwarding. Therefore, terminal nodes simultaneously undertake data collection and relay routing functions. Continuous wake-up and listening cause a surge in power consumption, making it impossible to support the long-term operation of lightweight battery-powered terminals. Multi-hop transmission relies on a single frequency point, and the co-frequency interference between adjacent nodes is severe. Furthermore, relay forwarding consumes bandwidth, resulting in the actual number of connected terminals per gateway being far lower than the theoretical value. When a terminal is bound to a fixed parent node, it needs to be manually reconnected when moving across regions. It cannot automatically switch relay paths, which leads to communication interruption.

[0015] In view of the inventors’ above-mentioned research findings, this application provides a hybrid network architecture, networking method and system based on LoRa and MESH to solve at least one of the above-mentioned technical problems.

[0016] Specifically, the hybrid network architecture of this application uses dedicated backbone nodes to act as Mesh relays (Mesh relay ends), and terminals only need to maintain LoRa star connections, effectively reducing power consumption; it adopts three-frequency group unit reuse, with different channels for backbone nodes within the group, avoiding co-channel interference between adjacent nodes, and frequency reuse between groups, effectively improving spectrum utilization and supporting massive terminal access; terminals can automatically roam and switch to the optimal backbone node channel based on signal strength, achieving seamless cross-group access.

[0017] The hybrid network architecture based on LoRa and Mesh provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0018] Figure 1 This is a schematic diagram of a hybrid network architecture based on LoRa and Mesh provided in an embodiment of this application, as shown below. Figure 1 As shown, this hybrid network architecture can include multiple hybrid network backbone nodes. For simplicity, the hybrid network backbone nodes will be referred to as backbone nodes below. Each backbone node can include a LoRa access terminal 101, a Mesh relay terminal (M) 102, and a channel management unit (CH) 103. That is, the hybrid network backbone node can simultaneously integrate the terminal connection function of the LoRa access terminal, the backbone networking function of the Mesh relay terminal, and the protocol conversion function of the channel management unit.

[0019] Specifically, the LoRa access terminal 101 is configured to establish a star-shaped connection with multiple user terminals in the access layer network using configurable channel frequencies within the same frequency band.

[0020] Among them, the channel frequency points of the LoRA access terminals of adjacent backbone nodes are different, such as Figure 1 As shown, the LoRa access terminals of multiple backbone nodes are configured as L1, L2, and L3 channels, respectively.

[0021] User terminals can be configured to automatically roam and switch to the channel frequency of the target backbone node based on signal strength, so as to achieve roaming access across backbone nodes.

[0022] As a concrete example, such as Figure 2 As shown, the group unit contains three hybrid backbone nodes. The LoRa access terminals in the three backbone nodes have different channel frequencies, configured as L1, L2, and L3 channels respectively. Each LoRa access terminal can connect to multiple user terminals and establish a star connection relationship. The same LoRa access terminal and its connected user terminals all communicate using the same channel frequency. When the current signal strength of a user terminal is low, it can automatically roam and switch to other channel frequencies. Figure 2As shown, in the same group of units, the user terminal can switch between three channel frequency points. For example, it can roam from L1 to L2, from L1 to L3, from L2 to L1, from L2 to L3, from L3 to L1, and from L3 to L2, depending on the detected real-time signal strength.

[0023] Mesh relay 102 is configured to communicate using a single fixed frequency in the backbone network and to establish multi-hop mesh connections with adjacent backbone nodes.

[0024] The channel management unit 103 is configured to establish a data pass-through channel through the pipe communication protocol and connect the LoRA access end and the Mesh relay end, convert the data packets of the LoRA access end into the Mesh protocol format in real time, and convert the data packets of the Mesh relay end into the LoRA protocol format in real time.

[0025] Among them, such as Figure 1 As shown, the hybrid network architecture is deployed in groups of three backbone nodes as a unit 10. Multiple groups of units are extended through inter-group connection links to form a multi-layer topology network. The three LoRA access terminals in each group of units are configured with three different channel frequencies. Multiple groups of units within the same preset area reuse the three channel frequencies.

[0026] As a concrete example, in a smart agriculture greenhouse networking scenario, each unit covers three greenhouses, corresponding to backbone nodes A, B, and C. Node A uses frequency F1 (868.1MHz), B uses F2 (868.3MHz), and C uses F3 (868.5MHz). The three greenhouses in other units can also reuse frequencies F1, F2, and F3. Inter-units are directly connected via Mesh relays, such as a fixed 2.4GHz frequency. Humidity data is converted via a pipeline communication protocol and then transmitted across units to the control center.

[0027] It should be noted that this application does not specifically limit the number of group units within the hybrid network architecture, such as... Figure 1 As shown, this hybrid network architecture can contain n group units 10, namely group 1 to group n, and n can be set to any value according to actual deployment requirements.

[0028] The Pipeline Communication Protocol (PCP) is a real-time duplex protocol that uses memory mapping technology to achieve line-rate conversion between LoRa and Mesh data packet formats. The channel management unit is specifically configured to: strip the LoRaWAN protocol header from the channel data packets received by the LoRa access point, add a Mesh routing header, and then pass them through to the Mesh relay end; remove the Mesh routing header from the data packets received by the Mesh relay end, encapsulate them in LoRaWAN format, and then send them to the user terminal through a designated channel. The user terminal can be a smartphone, tablet, laptop, desktop computer, wearable electronic device, etc.

[0029] The hybrid network architecture based on LoRa and Mesh provided in this application combines Mesh self-organizing networks with LoRa central networking to form a novel wireless communication network architecture that integrates lines, planes, and areas. It fully leverages the wireless extension characteristics of Mesh self-organizing networks as the backbone network for lines and planes, while utilizing the advantages of LoRa—low cost, low power consumption, light weight, small size, and long operating time—to enable large-scale deployment of user terminals. Furthermore, in this hybrid network structure, the Mesh relays of the backbone nodes fully undertake routing functions and maintain the backbone topology. The channel management unit of the backbone nodes shields the terminals from awareness of the Mesh protocol through protocol conversion. Based on this, user terminals only establish a star connection with the LoRa access points of the backbone nodes and only need to listen to the channel information of the LoRa access points, without participating in the multi-hop routing of the Mesh relays, thus eliminating the energy burden of data relay. Meanwhile, the hybrid network architecture deploys in groups of three backbone nodes, with each backbone node using a different channel to avoid co-channel interference between adjacent nodes. Frequency reuse between groups effectively improves spectrum utilization and supports massive terminal access. Multiple groups can be extended through inter-group links to form a multi-layered topology network. Thus, this hybrid network structure can achieve large-area, long-distance wireless network coverage while simultaneously enabling lightweight user terminals, reducing deployment and usage costs, and allowing for unlimited deployment numbers, effectively broadening its applicability.

[0030] The hybrid network architecture based on LoRa and Mesh will be described in detail below with reference to specific implementation examples.

[0031] In some embodiments of this application, in order to reduce co-channel interference between adjacent group units at the same frequency, the following channel multiplexing strategy is satisfied among multiple group units in the hybrid network architecture: the distance between the two backbone nodes corresponding to the LoRa access terminals using the same channel frequency in adjacent group units is greater than or equal to N times the coverage radius of a single node; the inter-group connection link is directly connected or hopped from the Mesh relay terminal of the backbone node of the multiplexed channel.

[0032] Specifically, N is the interference suppression coefficient, which can be set to a positive integer, such as 3 to 7 or other values. The single-node coverage radius refers to the straight-line distance from the effective signal coverage boundary of a single node (such as a base station, gateway, or sensor node) to the node's location in a wireless communication network. The size of the radius depends on various factors, including node type, environmental conditions, and technical parameters. Inter-group connections are achieved through direct connections (point-to-point) or hop connections (multi-level forwarding) between Mesh relays. Backbone nodes of multiplexed channels refer to nodes in different group units configured with the same LoRa frequency. For example, if node A in group 1 and node D in group 2 both use F1, their Mesh relays must achieve a signal-to-noise ratio ≥ 20dB for direct communication.

[0033] In one example, N=3, and the coverage radius of a single node is 500m. For the smart agriculture greenhouse networking scenario described above, each unit covers 3 greenhouses, corresponding to backbone nodes A, B, and C respectively. Node A uses frequency F1 (868.1MHz), node B uses F2 (868.3MHz), and node C uses F3 (868.5MHz). If backbone nodes D, E, and F in adjacent units reuse frequencies F1, F2, and F3, then the distance between nodes on the same frequency, such as node A and node D, must be ≥1500m.

[0034] In another example, N=4, and the coverage radius of a single node is 200m. For the scenario of roaming in a logistics park, the distance between group unit 1 (warehouse area) and group unit 2 (sorting area) is 800 meters, and the distance between nodes of the same frequency (all using F1) must be ≥800m; the groups are directly connected by the Mesh relay ends of node B (group 1) and node E (group 2).

[0035] In this embodiment, the distance constraint of N times the coverage radius of a single node reduces co-channel interference between user terminals accessing different unit groups on the same channel frequency, ensuring reliable roaming handover. Mesh direct connection reduces hop count, thereby lowering end-to-end latency, while jump connections support obstacle avoidance transmission, automatically switching paths when encountering metal shelves to ensure high reliability of the backbone layer. Simultaneously, the aforementioned channel multiplexing strategy effectively reduces frequency requirements, lowers spectrum licensing costs, and optimizes resources.

[0036] In some embodiments of this application, the backbone nodes described above can be configured as follows: After the user terminal connects to the first backbone node, in the data transmission scenario, the LoRa access end of the first backbone node receives the original LoRa data packet sent by the user terminal, and parses the data link layer of the original LoRa data packet to obtain the target address corresponding to the original data packet. The channel management unit of the first backbone node retrieves the group unit routing table associated with the first backbone node to determine whether the second backbone node corresponding to the target address belongs to the same group unit as the first backbone node. The group unit routing table records the node IDs of all backbone nodes in the same group unit, as well as the terminal IDs connected to the backbone nodes in the group unit. If they belong to the same group of units, the LoRa access terminal of the first backbone node will directly forward the original LoRa data packet to the LoRa access terminal of the second backbone node, and the LoRa access terminal of the second backbone node will then send it to the data receiver. If they do not belong to the same group of units, the channel management unit of the first backbone node will encapsulate the original LoRa data packets into the Mesh protocol format, and then forward them from the Mesh relay end of the first backbone node to the Mesh relay end of the second backbone node through the backbone layer network, and then the second backbone node will send them to the data receiver.

[0037] Specifically, the first backbone node is the backbone node currently connected to by the user terminal. When the user terminal wants to send data to the data receiver, it first sends a raw LoRa data packet to the first backbone node it is currently connected to. This raw LoRa data packet is an unconverted data unit sent by the user terminal through the LoRa physical layer, containing a MAC frame header and network payload. The MAC frame header carries the source address and destination address. The destination address is the MAC address of the second backbone node, which is the home backbone node of the data receiver corresponding to the raw LoRa data packet, and the source address is the MAC address of the first backbone node.

[0038] The data link layer is used for encapsulation, addressing, and error control of data frames between nodes. Specifically, this refers to parsing the destination address in the data packet, which points to the home backbone node of the data receiver, i.e., the second backbone node.

[0039] The group unit routing table can be a data structure stored in the memory of the backbone node, recording the node IDs (i.e. MAC addresses) of all backbone nodes in the same group unit and a list of directly connected terminal IDs, which is used to quickly determine the data forwarding path.

[0040] The specific implementation process of the above scheme may include: Data reception and parsing: After the user terminal connects to the first backbone node, the LoRa access end of the first backbone node receives the original LoRa data packet, strips off the physical layer preamble, and extracts the target address of the data link layer, such as MAC_B pointing to the second backbone node; Routing table lookup: The channel management unit of the first backbone node searches the local group unit routing table to determine whether the destination address exists in the local group unit routing table. If it exists, it is determined that the first backbone node and the second backbone node are in the same group unit. For example, if the node ID range within the group unit is 0x0A-0x0C, and the destination address belongs to this range, then they are in the same group.

[0041] Direct forwarding within the same group: If the first and second backbone nodes belong to the same group unit, the channel management unit of the first backbone node establishes a direct channel through the pipeline communication protocol, coordinates the LoRa access terminals of the two backbone nodes to establish a point-to-point link, bypassing the Mesh protocol stack, and then the LoRa access terminal of the first backbone node transparently transmits the original LoRa data packets to the LoRa access terminal of the second backbone node. The LoRa access terminal of the second backbone node matches the target terminal (i.e., the data receiver) in the local access terminal list according to the data receiver terminal ID and directly sends the data.

[0042] Cross-group Mesh relay: If the first and second backbone nodes belong to different groups, the first backbone node converts the original LoRa data packets into Mesh protocol format by calling the channel management unit, and forwards them to the second backbone node via fixed frequency points in the backbone layer.

[0043] In this embodiment, the cross-node forwarding decision time is reduced from O(n) in traditional Mesh to O(1) by using a local query mechanism of the group unit routing table instead of broadcasting across the entire network. At the same time, direct connection channels within the same group unit are used to avoid protocol conversion overhead, thereby reducing the latency of data transmission in the same domain. Protocol conversion and Mesh relay in cross-group scenarios maintain the low power consumption characteristics of the terminal while ensuring wide-area coverage. The terminal does not need to be aware of multi-hop routing, which solves the problem of spectrum resource waste caused by "local traffic bypassing the backbone layer" in traditional hybrid networks.

[0044] In some embodiments of this application, the group unit routing table also records the temporary access sequence number bound to the terminal ID. The temporary access sequence number is used by the backbone node to address its subordinate user terminals. The backbone node is specifically configured as follows: If they do not belong to the same group of units, the channel management unit of the first backbone node removes the LoRaWAN protocol header of the original LoRa data packet and adds a Mesh routing header to generate a Mesh protocol frame. The Mesh routing header includes the source address, destination address, terminal ID of the data receiver, hop count limit and QoS identifier. The Mesh relay end of the first backbone node forwards the Mesh protocol frames to the Mesh relay end of the second backbone node through the backbone layer network. The Mesh relay end of the second backbone node decapsulates the Mesh protocol frame to obtain the terminal ID of the data receiver. The channel management unit of the second backbone node obtains the temporary access sequence number of the data receiver by querying the group unit routing table associated with the second backbone node and mapping the terminal ID to the temporary access sequence number in the LoRa domain. The LoRa access terminal of the second backbone node locates the physical channel of the terminal based on the temporary sequence number of the data receiver and sends the Mesh protocol frame to the data receiver.

[0045] Specifically, the LoRaWAN protocol header is the control field in the LoRa proprietary frame structure, containing the terminal device address (DevAddr), frame counter, and adaptive rate control bits. The Mesh routing header is a custom protocol header for the backbone network, which may include the source address, destination address, data receiver terminal ID, hop count limit, and Quality of Service (QoS) identifier. The data receiver terminal ID is the terminal identifier, which is bound to a temporary access sequence number. The temporary access sequence number is assigned when the data receiver connects to the second backbone node and is not globally unique. It is used by the backbone node to accurately address its downstream user terminals, such as a 16-bit short address 0xFE2B. The hop count limit is the Time to Live (TTL) value, used to prevent data packets from looping indefinitely. QoS is a management mechanism in network technology that ensures that critical applications (such as voice and video) can still obtain low-latency, high-reliability transmission services even when the network is congested by classifying, prioritizing, and scheduling data streams. The QoS identifier is a 3-bit priority code, such as 101 indicating a real-time voice stream.

[0046] When cross-group forwarding is required, the channel management unit of the first backbone node removes the LoRaWAN protocol header, stripping the device address, frame counter, and other fields from the original LoRa data packet; it adds a Mesh routing header: filling in the source address (first backbone node MAC), destination address (second backbone node MAC), data receiver terminal ID (extracted from the payload of the original LoRa data packet), hop count limit, and QoS identifier (set according to the service type); Mesh protocol frame generation: encapsulating the original data payload into a Mesh protocol frame, including a routing header and encrypted payload; The Mesh relay of the first backbone node broadcasts to the adjacent second backbone node. After receiving the Mesh protocol frame, the Mesh relay of the second backbone node decapsulates the Mesh protocol header to obtain the terminal ID of the data receiver.

[0047] For example, when node B receives a water valve opening command from terminal #456, whose target address is terminal #789 and belongs to group 3, its encapsulation process is as follows: strip the original packet [MHDR | DevAddr#456 | FPort | Command Data], retain [#456 | Command Data]; add Mesh header [Source MAC=B | Target MAC=C | TTL=8 | QoS=1] + payload, and then broadcast it to the backbone layer.

[0048] In this embodiment, by precisely stripping the LoRaWAN protocol header and reconstructing key fields of the Mesh routing header, the amount of data in cross-group packets is reduced, protocol header redundancy is avoided, and backbone spectrum utilization is improved. The introduction of hop count limits and QoS identifiers can prevent network congestion and ensure end-to-end latency for high-priority services (such as alarm signals), solving the real-time performance loss problem caused by the lack of traffic classification mechanism in cross-domain transmission in traditional LoRa-Mesh hybrid networks. The temporary access sequence number of the data receiver is used to achieve accurate addressing and communication of devices within the local area network at the data link layer. This localized mapping mechanism (non-global address) avoids the overhead of backbone layer broadcast addressing and reduces Mesh relay power consumption. Furthermore, by enabling terminal cross-group addressing through the Mesh routing header, the problem of cross-network domain data transmission after terminal roaming is solved, achieving seamless roaming for the terminal.

[0049] In some embodiments of this application, the channel management unit is further configured to: monitor the signal strength of the user terminal in real time, and trigger the user terminal to perform channel switching and access the target backbone node based on the signal strength threshold; The backbone nodes are also configured to: assign temporary access sequence numbers to newly connected user terminals based on a sequential strategy, and bind the temporary access sequence numbers to the terminal IDs of the user terminals; The sequential strategy includes: if the first user terminal exits the LoRa access terminal of the target backbone node, then among the remaining user terminals still connected to the LoRa access terminal, the temporary access sequence number of the second user terminal that connects to the target backbone node after the first user terminal is moved forward by one sequence number.

[0050] Specifically, the signal strength threshold is a preset Received Signal Strength Indication (RSSI) threshold value, which is used to determine whether the link quality between the user terminal and the current backbone node meets the communication requirements. It can be set according to the needs, and this application does not make specific limitations on it. For example, it can be set to trigger the handover when RSSI ≤ -110dBm.

[0051] Channel switching can be the process by which a user terminal actively switches from the LoRa channel of the current backbone node to the channel of a target backbone node with a stronger signal, and access authentication needs to be performed again.

[0052] Temporary access sequence number is a dynamic identifier assigned by the backbone node to the user terminal for access. It is used to distinguish multiple terminals under the same channel and is bound to the terminal ID but is not permanently mapped.

[0053] For example, if a backbone node can connect to 256 user terminals, the temporary access sequence number can be 1-255 for fast addressing. Binding and sequence number shifting can be implemented using a hash table (Key=Terminal ID, Value=Sequence Number). When a terminal exits, a linked list structure reorganization is triggered, and the sequence number of subsequent terminals is decremented by 1 to avoid empty sequence numbers.

[0054] For example, node C connects to terminals #101 (serial number 1), #102 (serial number 2), and #103 (serial number 3). Therefore, before #102 exits, it is { #101:1, #102:2, #103:3}, and after exiting, it is { #101:1, #103:2}.

[0055] As a specific implementation, the channel management unit collects the terminal's RSSI in real time, for example, 4 times per second. When the RSSI is below the threshold of -85dBm for 3 consecutive times, a handover command is sent to the terminal, carrying the target backbone node ID and channel parameters. The target backbone node allocates temporary sequence numbers according to the first-come, first-served principle. For example, a new terminal is assigned the current maximum sequence number + 1, and the terminal ID (such as the device MAC address) and temporary sequence number are bound in the local mapping table. When a terminal exits due to timeout failure, its temporary sequence number is released, and the sequence numbers of subsequent terminals are shifted forward in sequence. For example, if the terminal with the original sequence number 3 exits, the terminal with the original sequence number 4 will be changed to the terminal with the new sequence number 3, ensuring that the sequence numbers are continuous and without gaps.

[0056] Thus, by using a dynamic signal strength-triggered switching mechanism, packet loss caused by weak signals is avoided, reducing data transmission latency. Combined with the continuous maintenance of temporary access sequence numbers, backbone nodes can quickly locate terminals, improving addressing efficiency. At the same time, by dynamically reclaiming temporary access sequence numbers, memory consumption caused by sequence number fragmentation is reduced, significantly optimizing resource utilization and access reliability in large-scale terminal roaming scenarios.

[0057] In some embodiments of this application, multiple user terminals connected to the same LoRa access point are associated with different data transmission time windows, and the user terminals are configured to send data within their associated data transmission time windows.

[0058] The data transmission time window is a fixed time slot pre-allocated to each terminal under the same LoRa access point. The LoRa channel time slot is divided into equal-length windows, such as 10ms per window. Within the window, the terminal has exclusive channel transmission rights, while outside the window, it remains silent. The association can be confirmed by querying the binding mapping table between the terminal ID and the time window (e.g., terminal A is bound to time slots 1-10ms). The backbone node initializes the allocation and synchronizes it to all terminals.

[0059] Specifically, when a terminal connects, the backbone node allocates windows according to the current load using an equal-interval polling algorithm and broadcasts the window allocation table through beacon frames. Terminals only send data within their own bound window (e.g., terminal B sends data in a 20-30ms window), while other windows automatically switch to receive mode, strictly avoiding co-channel conflicts through time isolation.

[0060] For example, to avoid collisions when sending data, a data window rule is established between the backbone node and the LoRA user terminal. The starting event point is fixed at 0:00:00:00 every day (hour:minute:second:millisecond), the transmission time of each terminal is T0 milliseconds, the number of user terminals currently connected to the LoRA access terminal is P, the sequence number of the user terminal is x, and the number of records per cycle is K. Then, the fixed transmission window time of each connected LoRA user terminal is (K-1)×PT0+x×T0.

[0061] In this embodiment, a hard time slot isolation mechanism is employed to allocate different data transmission time windows to multiple user terminals connected to the same LoRa access terminal, achieving time window isolation. This significantly reduces the probability of terminal collisions, eliminates data conflicts between multiple terminals on the same node, and lowers the conflict rate. Simultaneously, it provides deterministic transmission opportunities for low-power terminals, extending battery life. This is particularly suitable for periodic reporting scenarios such as industrial sensors, ensuring that critical data is transmitted without contention within a fixed time window.

[0062] In some embodiments of this application, the user terminal is further configured to: when there is data to be sent, monitor whether the channel in the current data transmission time window not associated with the user terminal is idle; if it is idle, send the data after a random backoff delay in the current data transmission time window associated with other user terminals.

[0063] The user terminal can monitor channel idleness through Clear Channel Assessment (CCA) by detecting the LoRa channel energy within a non-associated data transmission window, such as by performing an RSSI scan. If the energy level remains below the idle threshold (e.g., -100dBm), the channel is considered idle. This application allows the user terminal to transmit data when idleness is detected within a non-associated data transmission window, but a backoff mechanism is required. The random backoff delay refers to a randomly generated waiting time before the user terminal transmits data within the idle window, such as a random delay of 0-5ms to avoid the main window terminal.

[0064] Specifically, when the terminal has urgent data (such as an alarm signal) and is currently in an unbound window, it continuously monitors the channel RSSI. For example, if it is below -100dBm for 2 consecutive ms, it is considered idle. The terminal generates a random backoff time (based on a binary exponential backoff algorithm), and immediately sends data after the timeout. If a collision is detected during transmission, the backoff window is doubled to retry.

[0065] In this embodiment, the idle channel reuse mechanism with unbound windows ensures conflict-free transmission of periodic services while supporting low-latency preemptive transmission of emergency data, thus prioritizing emergency services. The backoff mechanism reduces the probability of sudden traffic conflicts, avoids preemptive conflicts, and achieves efficient coexistence of regular and emergency services. The idle time window is used to improve channel utilization and realize resource reuse.

[0066] In some embodiments of this application, multiple hybrid network backbone nodes and multiple user terminals within the hybrid network architecture are synchronized with a clock based on BeiDou satellite timing.

[0067] Specifically, based on the atomic clock time signal (accuracy ±100ns) broadcast by the BeiDou satellite, absolute time synchronization of all network devices is achieved. All backbone nodes and user terminals periodically calibrate their local clocks to the BeiDou standard time, with an error tolerance range of ±1μs.

[0068] The backbone nodes have a built-in BeiDou radio positioning service module that receives BeiDou time (BDC) signals with an accuracy of ±100ns. User terminal synchronization is achieved by broadcasting synchronization frames through the backbone nodes. These frames contain the current time window number and the BeiDou timestamp, and the terminal's local clock calibration error is ≤1μs.

[0069] In one example, at 0:00 every day, the backbone node receives the BeiDou timestamp and generates a synchronization frame broadcast. After receiving the synchronization frame, terminal #201 calibrates its local clock, reducing the original deviation of -2.3ms to 0ms, and reports stress data to all user terminals in a unified time window, such as window number = BDT seconds mod 60.

[0070] In another example, the backbone node obtains Coordinated Universal Time (UTC) through the BeiDou receiving module and sends a time synchronization beacon frame (containing a BeiDou timestamp) every 60 seconds. Upon receiving the frame, the terminal immediately calibrates its local clock. Window alignment is guaranteed: the start time of the time window is based on BeiDou time (e.g., time slot 1 = 0-10ms within a UTC second), and the terminal precisely triggers the window operation according to the calibrated local clock.

[0071] In this embodiment, BeiDou satellite time synchronization is performed through multiple hybrid network backbone nodes and multiple user terminals, eliminating clock drift between nodes, reducing time window alignment errors, ensuring time division multiplexing accuracy, and achieving microsecond-level synchronization. Furthermore, satellite time synchronization is not affected by terrain obstruction and has strong anti-interference capabilities.

[0072] In some embodiments of this application, a networking method based on LoRa and Mesh is provided, applied to the hybrid network architecture based on LoRa and Mesh in the above embodiments. The hybrid network architecture includes multiple hybrid network backbone nodes, each backbone node comprising a LoRa access terminal, a Mesh relay terminal, and a channel management unit. The method includes: In the access layer network, the LoRa access terminal establishes a star-shaped connection with multiple user terminals using configurable channel frequencies within the same frequency band. The channel frequencies of the LoRa access terminals of adjacent backbone nodes are different. The user terminal is configured to automatically roam and switch to the channel frequency of the target backbone node based on the signal strength, so as to realize roaming access across backbone nodes. Mesh relays use a single fixed frequency to communicate in the backbone network and establish multi-hop mesh connections with adjacent backbone nodes. The channel management unit establishes a data pass-through channel through the pipeline communication protocol and connects the LoRA access end and the Mesh relay end. It converts the data packets of the LoRA access end into the Mesh protocol format in real time, and converts the data packets of the Mesh relay end into the LoRA protocol format in real time. The hybrid network architecture is deployed in groups of three backbone nodes. Multiple groups of units are extended through inter-group connection links to form a multi-layer topology network. The three LoRA access terminals in each group of units are configured with three different channel frequencies. Multiple groups of units within the same preset area share the three channel frequencies. The preset area can be set according to specific needs, and this application does not make specific limitations on it.

[0073] The networking method based on LoRa and Mesh provided in this application combines Mesh self-organizing networks with LoRa central networking to form a novel wireless communication network architecture that integrates lines, planes, and areas. It fully leverages the wireless extension characteristics of Mesh self-organizing networks as the backbone network for lines and planes, while utilizing the advantages of LoRa—low cost, low power consumption, light weight, small size, and long operating time—to enable large-scale deployment of user terminals. Furthermore, in this hybrid network structure, the Mesh relays of the backbone nodes fully undertake routing functions and maintain the backbone topology. The channel management unit of the backbone nodes shields the terminals from awareness of the Mesh protocol through protocol conversion. Based on this, user terminals only establish a star connection with the LoRa access points of the backbone nodes and only need to listen to the channel information of the LoRa access points, without participating in the multi-hop routing of the Mesh relays, thus eliminating the energy burden of data relay. Meanwhile, the hybrid network architecture deploys in groups of three backbone nodes, with each backbone node using a different channel to avoid co-channel interference between adjacent nodes. Frequency reuse between groups effectively improves spectrum utilization and supports massive terminal access. Multiple groups can be extended through inter-group links to form a multi-layered topology network. Thus, this hybrid network structure can achieve large-area, long-distance wireless network coverage while simultaneously enabling lightweight user terminals, reducing deployment and usage costs, and allowing for unlimited deployment numbers, effectively broadening its applicability.

[0074] In some embodiments of this application, a LoRa and Mesh-based networking system is provided, including the hybrid network architecture based on LoRa and Mesh as described in the above embodiments. The system includes: multiple hybrid network backbone nodes, each backbone node including a LoRa access terminal, a Mesh relay terminal, and a channel management unit, wherein: the LoRa access terminal is used to establish a star-shaped connection with multiple user terminals in the access layer network using configurable channel frequencies within the same frequency band, wherein the channel frequencies of the LoRa access terminals of adjacent backbone nodes are different, and the user terminals are configured to automatically roam and switch to the channel frequency of the target backbone node based on signal strength to achieve roaming access across backbone nodes; the Mesh relay terminal is used to... The backbone network uses a single fixed frequency for communication and establishes multi-hop mesh connections with adjacent backbone nodes. The channel management unit is used to establish a direct data channel through the pipeline communication protocol and connect the LoRA access terminal and the Mesh relay terminal. It converts the data packets of the LoRA access terminal into Mesh protocol format in real time and converts the data packets of the Mesh relay terminal into LoRA protocol format in real time. The hybrid network architecture is deployed in groups of three backbone nodes. Multiple groups of units are extended through inter-group connection links to form a multi-layer topology network. The three LoRA access terminals in each group of units are configured with three different channel frequencies. Multiple groups of units within the same preset area reuse the three channel frequencies.

[0075] The LoRa and Mesh-based networking system provided in this application combines Mesh self-organizing networks with LoRa central networking to form a novel wireless communication network architecture that integrates lines, planes, and areas. It fully leverages the wireless extension characteristics of Mesh self-organizing networks as the backbone network for lines and planes, while utilizing the advantages of LoRa—low cost, low power consumption, light weight, small size, and long operating time—to enable large-scale deployment of user terminals. Furthermore, in this hybrid network structure, the Mesh relays of the backbone nodes fully undertake routing functions and maintain the backbone topology. The channel management unit of the backbone nodes shields the terminals from awareness of the Mesh protocol through protocol conversion. Based on this, user terminals only establish a star connection with the LoRa access points of the backbone nodes and only need to listen to the channel information of the LoRa access points, without participating in the multi-hop routing of the Mesh relays, thus eliminating the energy burden of data relay. Meanwhile, the hybrid network architecture deploys in groups of three backbone nodes, with each backbone node using a different channel to avoid co-channel interference between adjacent nodes. Frequency reuse between groups effectively improves spectrum utilization and supports massive terminal access. Multiple groups can be extended through inter-group links to form a multi-layered topology network. Thus, this hybrid network structure can achieve large-area, long-distance wireless network coverage while simultaneously enabling lightweight user terminals, reducing deployment and usage costs, and allowing for unlimited deployment numbers, effectively broadening its applicability.

[0076] The networking method and system based on LoRa and Mesh provided in this application can achieve... Figure 1-2 The various processes implemented by the hybrid network architecture can achieve the same technical effects, and to avoid repetition, they will not be described in detail here.

[0077] Figure 3 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application.

[0078] like Figure 3 As shown, the electronic device 300 includes a memory 301, a processor 302, and a computer program stored in the memory 301 and executable on the processor 302.

[0079] In one example, the processor 302 described above may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0080] Memory 301 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the LoRa and Mesh-based networking method in the embodiments according to the second aspect of this application.

[0081] The processor 302 reads the executable program code stored in the memory 301 to run the computer program corresponding to the executable program code, so as to implement the networking method based on LoRa and Mesh in the second aspect embodiment above.

[0082] In some examples, the electronic device 300 may also include a communication interface 303 and a bus 310. For example, Figure 3 As shown, the memory 301, processor 302, and communication interface 303 are connected through bus 310 and complete communication with each other.

[0083] The communication interface 303 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application. Input devices and / or output devices can also be connected through the communication interface 303.

[0084] Bus 310 includes hardware, software, or both, that couples components of electronic device 300 together. For example, and not limitingly, bus 310 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 310 may include one or more buses. Although specific buses are described and illustrated in the embodiments of this application, this application considers any suitable bus or interconnection.

[0085] The electronic device provided in this application embodiment can realize the various processes implemented by the backbone node and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0086] In conjunction with the LoRa and MESH-based networking methods described in the above embodiments, this application can provide a computer storage medium for implementation. This computer storage medium stores computer program instructions; when executed by a processor, these computer program instructions implement the steps of any of the LoRa and MESH-based networking methods described in the above embodiments.

[0087] In conjunction with the LoRa and MESH-based networking methods described in the above embodiments, this application provides a computer program product for implementation. This (computer) program product is stored in a non-volatile storage medium, and when executed by at least one processor, it implements the steps of any of the LoRa and MESH-based networking methods described in the above embodiments.

[0088] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes implemented by the backbone nodes in the above-mentioned hybrid network architecture based on LoRa and MESH, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0089] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0090] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0091] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0092] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0093] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0094] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A networking system based on LoRa and Mesh, characterized in that, The networking system adopts a hybrid network architecture, and the networking system includes: Multiple hybrid network backbone nodes, each backbone node includes a LoRa access point, a Mesh relay point, and a channel management unit, wherein: The LoRa access terminal is configured to establish a star-shaped connection with multiple user terminals in the access layer network using configurable channel frequencies within the same frequency band. The channel frequencies of the LoRa access terminals of adjacent backbone nodes are different. The user terminals are configured to automatically roam and switch to the channel frequency of the target backbone node based on the signal strength, so as to realize roaming access across backbone nodes. Mesh relays are configured to communicate using a single fixed frequency in the backbone network and establish multi-hop mesh connections with adjacent backbone nodes. The channel management unit is configured to establish a data pass-through channel through the pipe communication protocol and connect the LoRA access end and the Mesh relay end, convert the data packets of the LoRA access end into the Mesh protocol format in real time, and convert the data packets of the Mesh relay end into the LoRA protocol format in real time. The hybrid network architecture is deployed in groups of three backbone nodes. Multiple groups of units are extended through inter-group connection links to form a multi-layer topology network. The three LoRA access terminals in each group of units are configured with three different channel frequencies. Multiple groups of units within the same preset area reuse the three channel frequencies. The backbone nodes are configured as follows: After the user terminal connects to the first backbone node, in the data transmission scenario, the LoRa access terminal of the first backbone node receives the original LoRa data packet sent by the user terminal, and parses the data link layer of the original LoRa data packet to obtain the target address corresponding to the original LoRa data packet. The target address is the MAC address of the second backbone node, and the second backbone node is the home backbone node of the data receiver corresponding to the original LoRa data packet. The channel management unit of the first backbone node retrieves the group unit routing table associated with the first backbone node to determine whether the second backbone node corresponding to the target address belongs to the same group unit as the first backbone node. The group unit routing table records the node IDs of all backbone nodes in the same group unit, as well as the terminal IDs connected to the backbone nodes in the group unit. If they belong to the same group of units, the LoRa access terminal of the first backbone node will directly forward the original LoRa data packet to the LoRa access terminal of the second backbone node, and the LoRa access terminal of the second backbone node will then send it to the data receiver. If they do not belong to the same group of units, the channel management unit of the first backbone node will encapsulate the original LoRa data packet into the Mesh protocol format, and then the Mesh relay of the first backbone node will forward it to the Mesh relay of the second backbone node through the backbone layer network, and then the second backbone node will send it down to the data receiver.

2. The system according to claim 1, characterized in that, The hybrid network architecture satisfies the following channel multiplexing strategy among multiple group units: the distance between the two backbone nodes corresponding to the LoRa access terminals using the same channel frequency in adjacent group units is greater than or equal to N times the coverage radius of a single node; the inter-group connection link is directly connected or hopped from the Mesh relay end of the backbone node of the multiplexed channel.

3. The system according to claim 1, characterized in that, The group unit routing table also records the temporary access sequence number bound to the terminal ID. This temporary access sequence number is used by the backbone node to address its downstream user terminals. The backbone node is specifically configured as follows: If they do not belong to the same group of units, the channel management unit of the first backbone node removes the LoRaWAN protocol header of the original LoRa data packet and adds a Mesh routing header to generate a Mesh protocol frame. The Mesh routing header includes the source address, destination address, terminal ID of the data receiver, hop count limit and QoS identifier. The Mesh relay end of the first backbone node forwards the Mesh protocol frame to the Mesh relay end of the second backbone node through the backbone layer network; The Mesh relay end of the second backbone node decapsulates the Mesh protocol frame to obtain the terminal ID of the data receiver; The channel management unit of the second backbone node obtains the temporary access sequence number of the data receiver by querying the group unit routing table associated with the second backbone node and mapping the terminal ID to the temporary access sequence number in the LoRa domain. The LoRa access terminal of the second backbone node locates the physical channel of the terminal based on the temporary sequence number of the data receiver and sends the Mesh protocol frame to the data receiver.

4. The system according to claim 1, characterized in that, The channel management unit is also configured to: monitor the signal strength of the user terminal in real time, and trigger the user terminal to perform channel switching and access the target backbone node based on the signal strength threshold; The backbone node is further configured to: assign temporary access sequence numbers to newly connected user terminals based on a sequential strategy, and bind the temporary access sequence numbers to the terminal ID of the user terminals; The sequential strategy includes: if the first user terminal exits the LoRa access terminal of the target backbone node, then among the remaining user terminals still connected to the LoRa access terminal, the temporary access sequence number of the second user terminal that connects to the target backbone node after the first user terminal is shifted forward by one sequence number.

5. The system according to claim 1, characterized in that, Multiple user terminals connected to the same LoRa access point are associated with different data transmission time windows, and the user terminals are configured to send data within their associated data transmission time windows.

6. The system according to claim 5, characterized in that, The user terminal is further configured to: when there is data to be sent, monitor whether the channel in the current data transmission time window not associated with the user terminal is idle; if it is idle, send the data after a random backoff delay in the current data transmission time window associated with other user terminals.

7. The system according to claim 1 or 5, characterized in that, The hybrid network architecture includes multiple hybrid network backbone nodes and multiple user terminals that are synchronized with the clock based on the BeiDou satellite timing.

8. A networking method based on LoRa and Mesh, characterized in that, Applied to the networking system as described in any one of claims 1-7, the hybrid network architecture in the networking system includes multiple hybrid network backbone nodes, each backbone node comprising a LoRa access terminal, a Mesh relay terminal, and a channel management unit, the method comprising: In the access layer network, the LoRa access terminal establishes a star-shaped connection with multiple user terminals using configurable channel frequencies within the same frequency band. The channel frequencies of the LoRa access terminals of adjacent backbone nodes are different. The user terminals are configured to automatically roam and switch to the channel frequency of the target backbone node based on the signal strength, so as to realize roaming access across backbone nodes. Mesh relays use a single fixed frequency to communicate in the backbone network and establish multi-hop mesh connections with adjacent backbone nodes. The channel management unit establishes a data pass-through channel through the pipeline communication protocol and connects the LoRA access end and the Mesh relay end. It converts the data packets of the LoRA access end into the Mesh protocol format in real time, and converts the data packets of the Mesh relay end into the LoRA protocol format in real time. The hybrid network architecture is deployed in groups of three backbone nodes. Multiple groups of units are extended through inter-group connection links to form a multi-layer topology network. The three LoRA access terminals in each group of units are configured with three different channel frequencies. Multiple groups of units within the same preset area reuse the three channel frequencies.

Images