An application method through self-organizing network protocol

Abstract

The present invention proposes an application method through a self-organizing network protocol, which includes the following steps: S1: networking through a fully peer-to-peer Mesh structure, in which all nodes are completely peer-to-peer and cooperate with each other to complete network establishment, routing forwarding and communication; S2: dividing the same devices in different areas or different devices in the same area into different networks, distinguishing different networks through network IDs, and using different channels in different networks to physically isolate the networks; S3: a single network exchanges data through unicast communication and broadcast communication. When unicast communication is selected, unicast communication is performed through the unique ID set in each device as the communication address; S4: when broadcast communication is adopted, interaction is performed through a master-slave communication mechanism. The communication is initiated by a set host and interacted through nodes. The nodes wait for the host command to respond, and the slave end does not exchange data with other slave nodes.

Description

Technical Field

[0001] The invention belongs to the field of self-organizing networks, and in particular relates to an application method through a self-organizing network protocol. Background Art

[0002] Currently, establishing a complete Zigbee network involves two steps: network initialization and adding nodes (routers or terminals) to the network. The standard Zigbee network protocol includes a coordinator, routers, and terminal nodes. Setting up a Zigbee network requires not only a coordinator but also routers or terminal nodes.

[0003] Each device in a network must have a unique short address. When a node joins the network, it is assigned by its parent node and communicates using the short address. For the coordinator, the short address is typically set to 0x0000. After completing the above steps, the Zigbee mesh network is successfully initialized and then waits for other nodes to join. Node joining the network involves two steps: connecting to the coordinator and joining the network through an existing parent node. Summary of the Invention

[0004] The present invention proposes an application method through a self-organizing network protocol, which solves the problem that the existing protocol stack in the prior art requires pre-setting of device functions, and all devices cannot have the same function, which may result in a fixed central node in the network, making the network inflexible; and for fixed application scenarios, the position of the device remains unchanged, the advantages of the self-organizing network no longer exist, but the time and resources consumed by the self-organizing network are still high.

[0005] The technical solution of the present invention is implemented as follows: an application method through an ad hoc network protocol, the method comprising the following steps: S1: networking through a fully peer-to-peer Mesh structure, with all nodes being completely peer-to-peer and collaborating to complete network establishment, routing, forwarding, and communication; S2: dividing the same devices in different areas or different devices in the same area into different networks, distinguishing the different networks by network IDs, and using different channels in the different networks for physical network isolation; S3: a single network exchanges data through unicast communication and broadcast communication. When unicast communication is selected, unicast communication is performed using a unique ID set in each device as the communication address; S4: when broadcast communication is used, interaction is performed through a master-slave communication mechanism, with communication initiated by a set host and interaction performed through nodes. The nodes wait for host commands to respond, and the slave end does not exchange data with other slave nodes; S5: when the supervisory end module is running, it does not participate in the network access process and exchanges data through a point-to-point communication mechanism that quickly binds slaves and communicates. The host manages the nodes through a management process and adjusts the node status according to the host's needs to complete data interaction between the host and the slave.

[0006] Currently, the general network initialization process is as follows:

[0007] 1) Determine the network coordinator. First, determine whether the node is an FFD node. Then determine whether this FFD node is in another network or whether a coordinator already exists in the network. Through active scanning, send a beacon request command (Beacon request command), and then set a scan period. If no beacon is detected within the scan period, it is assumed that the FFD has no coordinator in its POS. At this time, it can establish its own Zigbee network and continuously generate and broadcast beacons as the coordinator of this network.

[0008] 2) Perform channel scanning. This includes two processes: energy scanning and active scanning. First, perform energy detection on the designated channel or the default channel to avoid possible interference. Sort the channels in ascending order based on the measured energy values, discard channels whose energy values ​​exceed the allowable energy level, select channels with allowable energy levels and mark them as available channels. Then perform active scanning to search for network information within the communication radius of the node. This information is broadcast in the network in the form of beacon frames. The node obtains these beacon frames through active channel scanning, and then finds the best and relatively quiet channel based on this information. Based on the recorded results, select a channel that should have the least Zigbee networks, preferably no Zigbee devices. During active scanning, the MAC layer will discard all frames received by the PHY layer data service except beacons.

[0009] 3) Configure network parameters (set network ID). After finding a suitable channel, the coordinator will select a network identifier (PAN ID, value <= 0x3FFF) for the network. This ID must be unique within the channel being used and cannot conflict with other Zigbee networks. The PAN ID can be obtained by listening to the IDs of other networks and selecting an ID that does not conflict, or by manually specifying the scan channel and then determining a PAN ID that does not conflict with other networks. There are two address modes in the Zigbee network: extended address (64 bits) and short address (16 bits). The extended address is assigned by the IEEE organization and is used to uniquely identify devices; the short address is used to identify devices within the local network.

[0010] As a preferred embodiment, the Mesh structure networking in step S1 adopts a full peer-to-peer network state network protocol stack, and adopts encrypted data transmission through a discrete routing algorithm and in the underlying layer and data transmission process to ensure the security of the transmitted data. Through the Mesh structure networking, only adjacent information is recorded, stored and updated during networking.

[0011] As a preferred embodiment, in step S2, several routing nodes are set up in different networks, and the routing nodes have the independent right to choose the next hop for transmitting data packets. When the network topology changes and the path is lost, the routing nodes will try their best to transmit it to the optimal next hop node.

[0012] As a preferred embodiment, in step S2, when performing physical isolation, isolation is performed by setting a physical channel. When setting the physical channel, the user can set the range to 0x00~0x7F. When the highest bit bit7 of the user-set value is set to 1, the values ​​of bit0~bit6 are invalid, and the channel is automatically configured according to the network ID.

[0013] As a preferred embodiment, when broadcast communication is adopted in step S4, if the Zigbee module is set as the host side, data forwarding is performed according to the address specified by the collector, and when the slave side module is running, it only accepts data from the host side and the supervisor side, and forwards the data to each other, and the slave side does not exchange data with other slave nodes.

[0014] As a preferred implementation, the management process of the host in step S5 is as follows: S51: first perform a reset and power-on serial port adapter operation, and then synchronize the list; S52: determine the connection status of the test whitelist node, update its connection status, and update the topology relationship. After updating the topology relationship, cache the original topology relationship; S53: after completing the topology relationship update, the host sends a heartbeat process, and then performs data communication processing, and then updates the connection status while performing data communication processing; S54: finally enter the network maintenance process.

[0015] As a preferred embodiment, the node includes three states, state one is off-network and unregistered state, state two is off-network and registered state, and state three is on-network and registered state; where off-network means that the node has not found the host heartbeat since it was powered on, has not tested the host connection or the host connection test has failed; unregistered means that the node has no host information record saved and is a blank node; whether the node is on the network is determined by testing whether the host exists based on the recorded host and network information, thereby confirming whether the machine has been on the network, and at the same time notifying the host of the node's network status through this process.

[0016] After adopting the above technical solution, the beneficial effects of the present invention are as follows: based on the existing protocol stack, the device functions need to be pre-set, and all devices cannot have the same function, resulting in the network having a fixed central node, which makes the network inflexible. The present invention provides a networking method based on ZigBee that does not require a fixed center and pre-set device types, so that all nodes can independently form and join the network without any human intervention and ensure that the network can still operate normally after any node failure occurs. In the present invention, each device can dynamically identify network information and dynamically adjust its own identity to operate normally. Dynamic fusion can also be achieved in multiple networks so that network information does not cross. Therefore, the present invention can dynamically and adaptively form a centerless dynamic network in complex environments and special scenarios, ensuring that the network can still communicate normally in the event of a dynamic failure without the need for human intervention. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0018] Figure 1 This is a diagram of the full peer-to-peer distributed network structure of the present invention;

[0019] Figure 2 This is a diagram of the network structure of the invention's rapid topology adaptation (when a node moves, a new path can be quickly established);

[0020] Figure 3 This is a network structure diagram of the fast path repair (when a node path fails, the node directly reroutes) of the present invention;

[0021] Figure 4 This is a schematic diagram of network division in the present invention;

[0022] Figure 5 This is a flow chart of host management of the present invention;

[0023] Figure 6 This is a flowchart of the node registration and network access processing of the present invention. DETAILED DESCRIPTION

[0024] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0025] Example:

[0026] like Figures 1 to 6 As shown, an application method through a self-organizing network protocol, the method includes the following steps: S1: networking through a fully peer-to-peer Mesh structure, all nodes are completely peer-to-peer, and cooperate with each other to complete network formation, routing forwarding and communication; S2: dividing the same devices in different areas or different devices in the same area into different networks, distinguishing different networks through network IDs, and using different channels in different networks for physical network isolation; S3: a single network exchanges data through unicast communication and broadcast communication. When unicast communication is selected, unicast communication is performed using the unique ID set in each device as the communication address; S4: when broadcast communication is used, interaction is performed through a master-slave communication mechanism, where the communication is initiated by a set host and interacted through nodes. The nodes wait for the host command to respond, and the slave end does not exchange data with other slave nodes; S5: when the supervisory end module is running, it does not participate in the network access process, and exchanges data through a point-to-point communication mechanism that quickly binds the slave and communicates. The host manages the node through the management process and adjusts the node status according to the host's needs to complete the data interaction between the host and the slave.

[0027] This application document adopts a discrete routing algorithm with fast networking speed, fast network topology response, efficient and stable communication; it uses encrypted transmission at the bottom layer and in the data transmission process, and the data transmission is safe and reliable.

[0028] Unlike traditional Zigbee ad hoc networking protocols, this protocol utilizes a fully peer-to-peer mesh structure, where all nodes are fully equal and collaborate to build the network, route forwarding, and communicate. It utilizes a distributed routing algorithm that only records, stores, and updates neighbor information during networking. As a result, it offers the following characteristics: 1. Large network capacity, enabling easy expansion; 2. Rapid response to topology changes, with strong adaptability to poor signal conditions; Fast path repair, high data transmission efficiency, and reliability; 3. Support for rapid changes and adaptation to network topology; 4. Rapid route repair; and 5. Insensitive communication to routing changes.

[0029] For ease of management, networking applications typically divide identical devices in different areas, or different devices in the same area, into different networks. This allows devices on the same network to communicate with each other, while devices on different networks remain isolated. Networks are uniquely distinguished by their "Network ID." If the "Network IDs" are different, devices with different "Network IDs" are logically isolated. To further isolate devices on different networks, different channels can be set to achieve physical network isolation. The user-configurable physical channel range is 0x00 to 0x7F. When the highest bit, bit 7, of the user-set value is set to 1, the values ​​of bits 0 to 6 are ignored, and the module automatically configures the channel based on the "Network ID." By default, the channel value is 0x80. The module logically uniquely divides networks based on the "Network ID" and automatically uses different (or possibly the same) channels to physically isolate networks.

[0030] Supports unicast communication and broadcast communication. When unicasting, the destination address needs to be specified. Therefore, a unique ID is assigned to each device, called the "local ID". When performing unicast communication, the "local ID" of the destination ID is specified as the destination address to achieve unicast communication. The specific network division is as follows Figure 4 shown.

[0031] Figure 4 The available channels shown in the figure physically separate different nodes, the network ID logically separates different nodes, and the local ID and destination ID specify the sender and receiver. However, these features are not yet fully applicable in practical applications. Key issues include: If too many nodes initiate communication simultaneously within a network, the network may become blocked or lose data. In some applications, network authorization is required, and unnecessary nodes are not permitted to participate. It would be desirable for nodes to automatically configure themselves and be assigned to different networks and channels without user intervention. (Proper network segmentation can prevent congestion in the same area.) Some communications do not require cross-routing and can only occur locally. To accommodate these situations, this module has built-in network management capabilities. The master-slave communication mechanism is the communication method used in most data acquisition systems. Each operation is initiated by the master, and the nodes only respond to the master's commands. Therefore, only one node is communicating at any given time, ensuring network stability. If the Zigbee module is configured as the master, it forwards data according to the address specified by the data collector. When the slave module is operating, it only receives data from the master and supervisor, and forwards data to each other. The slave node does not communicate with other slave nodes.

[0032] When the supervisory module is running, it does not participate in the network access process and does not require multi-relay routing forwarding. Therefore, the supervisory communication adopts a point-to-point communication mechanism that quickly binds the slave and communicates for data exchange. This module is based on the HYXQ-053B protocol stack and supports both routing and non-routing communication methods. For this solution, this design adopts a master-slave communication mechanism + point-to-point communication mechanism. The host management network host completes the following functions:

[0033] 1. Generate a unique and random network ID and set the network ID of the managed node to this ID.

[0034] 2. Send the host heartbeat so that the node can actively try to connect.

[0035] 3. Manage the whitelist and allow nodes with network access permissions to join the network.

[0036] 4. Management proactively reports and allows all devices to access the network as required.

[0037] 5. Manage and update the node online status. The host management process is as follows Figure 5 shown.

[0038] In step S1, the Mesh structure networking adopts a full peer-to-peer network state network protocol stack, and adopts encryption to transmit data through a discrete routing algorithm and in the underlying layer and data transmission process to ensure the security of the transmitted data. When networking, only adjacent information is recorded, stored and updated through the Mesh structure networking.

[0039] In step S2, several routing nodes are set in different networks. The routing nodes have the autonomy to select the next hop for transmitting data packets. When the network topology changes and the path is lost, the routing nodes will try their best to transmit the data packets to the optimal next hop node.

[0040] In step S2, when physical isolation is performed, isolation is performed by setting a physical channel. When setting the physical channel, the user can set the range to 0x00~0x7F. When the highest bit bit7 of the user-set value is set to 1, the values ​​of bit0~bit6 are invalid, and the channel is automatically configured according to the network ID.

[0041] When broadcast communication is adopted in step S4, if the Zigbee module is set as the host end, data forwarding is performed according to the address specified by the collector, and when the slave end module is running, it only accepts data from the host end and the supervisor end, and forwards the data to each other. The slave end does not exchange data with other slave nodes.

[0042] The management process of the host in step S5 is as follows: S51: first perform a reset and power-on serial port adapter operation, and then synchronize the list; S52: determine the connection status of the test whitelist node, update its connection status, and update the topology relationship. After updating the topology relationship, cache the original topology relationship; S53: after completing the topology relationship update, the host sends a heartbeat process, and then performs data communication processing, and then updates the connection status while performing data communication processing; S54: finally enter the network maintenance process.

[0043] The node includes three states, state one is off-network and unregistered state, state two is off-network and registered state, and state three is on-network and registered state; wherein off-network means that the node has not found the host heartbeat since it was powered on, has not tested the host connection or the host connection test was unsuccessful; unregistered means that the node has not saved the host information record and is a blank node; whether the node is on the network is determined by testing the existence of the host based on the recorded host and network information, thereby confirming whether the local machine has been on the network, and at the same time notifying the host of the node's network status through this process. Off-network means that the node has not found the host heartbeat since it was powered on, has not tested the host connection or the host connection test was unsuccessful. Unregistered means that the node has not saved the host information record and is a blank node. For an unregistered node, node network access refers to the process of searching for the host, requesting a connection, obtaining approval, and finally obtaining the corresponding network information.

[0044] For registered nodes, network access involves testing the host's presence based on recorded host and network information to confirm network access. This process also notifies the host of the node's network access status. If a node is registered but not yet networked, but fails to test the host, after a specified number of retries, the node will assume that the network information is incorrect or the host is missing and will proceed to the registration process.

[0045] The node access logic needs to be processed in conjunction with the host, and its logic is divided into node processing logic and host processing logic. This design supports two network access management methods: whitelist management and active reporting management. To better ensure the accuracy and reliability of network access, the network access registration process is divided into two methods: whitelist registration and active reporting registration. When a node accesses the network, it will first search for hosts using the whitelist method. If it fails (and the time allowed for active reporting access has expired), it will start searching for hosts that support active reporting and access the network. In other words, whitelist access has higher priority than active reporting access.

[0046] like Figure 6As shown in the figure, this module uses a whitelist mechanism to manage network and communication. When managing the network, the whitelist is used to determine the legitimacy of nodes. Automatic networking is achieved based on the user-provided whitelist (when self-reporting, if the node successfully joins the network, the host will also add the node to the list). During network operation, only nodes that are on the host's list can properly test the host status and achieve normal data communication. During communication, data sent by the node is filtered through the whitelist; data not on the list is ignored. The host sends data based on the whitelist; requests for data not on the list will return an error.

[0047] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. An application method through a self-organizing network protocol, characterized in that: The method comprises the following steps: S1: Through the full peer-to-peer Mesh structure networking, all nodes are completely equal and work together to complete network establishment, routing, forwarding and communication; S2: Divide the same devices in different areas or different devices in the same area into different networks, distinguish different networks by network ID, and use different channels in different networks for physical network isolation; S3: A single network exchanges data through unicast communication and broadcast communication. When unicast communication is selected, the unique ID set in each device is used as the communication address for unicast communication. S4: When broadcast communication is used, the interaction is carried out through the master-slave communication mechanism. The communication is initiated by the set host and interacted through the nodes. The nodes wait for the host command to respond, and the slave end does not exchange data with other slave nodes. S5: When the supervisory module is running, it does not participate in the network access process, and exchanges data through a point-to-point communication mechanism that quickly binds the slaves and communicates. The host manages the nodes through the management process and adjusts the node status according to the host's needs to complete the data interaction between the host and the slaves.

2. The application method according to claim 1, wherein: In step S1, the Mesh structure networking adopts a full peer-to-peer network state network protocol stack, and adopts encryption to transmit data through a discrete routing algorithm and in the underlying layer and data transmission process to ensure the security of the transmitted data. When networking, only adjacent information is recorded, stored and updated through the Mesh structure networking.

3. The application method according to claim 1, wherein: In step S2, several routing nodes are set in different networks. The routing nodes have the autonomy to select the next hop for transmitting data packets. When the network topology changes and the path is lost, the routing nodes will try their best to transmit the data packets to the optimal next hop node.

4. The application method according to claim 1, wherein: In step S2, when physical isolation is performed, isolation is performed by setting a physical channel. When setting the physical channel, the user can set the range to 0x00~0x7F. When the highest bit bit7 of the user-set value is set to 1, the values ​​of bit0~bit6 are invalid, and the channel is automatically configured according to the network ID.

5. The application method according to claim 1, wherein: When broadcast communication is adopted in step S4, if the Zigbee module is set as the host end, data forwarding is performed according to the address specified by the collector, and when the slave end module is running, it only accepts data from the host end and the supervisor end, and forwards the data to each other. The slave end does not exchange data with other slave nodes.

6. The application method according to claim 1, wherein: The host management process in step S5 is as follows: S51: First, perform a reset and power-on serial port adapter operation, and then synchronize the list; S52: Determine the connection status of the test whitelist node, update its connection status, and update the topology relationship. After the topology relationship is updated, cache the original topology relationship; S53: After completing the topology update, the host sends a heartbeat process, then performs data communication processing, and then updates the connection status while performing data communication processing; S54: Finally, enter the network maintenance process.

7. The application method according to claim 1, wherein: The node has three states: state 1 is not connected to the network and not registered; state 2 is not connected to the network and registered; state 3 is connected to the network and registered; where not connected to the network means that the node has not found the host heartbeat since it was powered on, has not tested the host connection or the host connection test has failed; unregistered means that the node has no host information record saved and is a blank node; Whether the node is connected to the network is determined by testing the host's existence based on the recorded host and network information, thereby confirming whether the local machine has been connected to the network. At the same time, this process notifies the host of the node's network status.

Images