A method for dynamically adjusting Zigbee device reporting strategy in a complex network environment

Abstract

The present invention discloses a method for dynamically adjusting a Zigbee device reporting strategy in a complex network environment, comprising the following steps: S1: Network and device status monitoring: collecting key status information of the network and the device in real time, and monitoring network parameters and device status according to the collected information. The present invention monitors the network and device status in real time, analyzes the network load and device importance, and dynamically generates an optimized reporting strategy, and sends it to the target device for dynamic adjustment. By dynamically adjusting the device reporting strategy, redundant communications in the network are reduced, channel occupancy and packet collision probability are reduced, and the reliability and efficiency of data transmission are improved, achieving efficient utilization of network resources and reduction of device power consumption, and can adapt to different application scenarios and network environments, with high flexibility and scalability.

Description

Technical Field

[0001] The present invention relates to the technical field of Zigbee devices, and in particular to a method for dynamically adjusting a Zigbee device reporting strategy in a complex network environment. Background Art

[0002] Zigbee is a low-power, low-rate wireless communication protocol based on the IEEE 802.15.4 standard. It is widely used in device connection and communication in smart home, Internet of Things and other fields. In existing smart home systems, Zigbee devices usually adopt a fixed reporting strategy, that is, the device reports data to the gateway according to a preset time interval or specific event trigger conditions;

[0003] However, in scenarios with a large number of devices and complex network topologies, fixed reporting strategies have the following defects: 1. Network congestion: A large number of devices reporting data at the same time may lead to fierce competition for channel resources, increase the probability of data packet collision and loss, and affect the reliability of communication; 2. High device power consumption: A fixed high-frequency reporting strategy will cause battery-powered devices to consume more power, shorten the battery life of the device, and increase maintenance costs; 3. Lack of flexibility: Existing strategies cannot be dynamically adjusted according to the network status and the importance of the device, resulting in low utilization of network resources and unable to adapt to complex and changing application scenarios; Based on the above, this application proposes a method for dynamically adjusting the reporting strategy of Zigbee devices in a complex network environment. Summary of the invention

[0004] Based on the technical problems existing in the background technology, the present invention proposes a method for dynamically adjusting the reporting strategy of Zigbee devices in a complex network environment.

[0005] The present invention proposes a method for dynamically adjusting a Zigbee device reporting strategy in a complex network environment, comprising the following steps:

[0006] S1: Network and device status monitoring: collect key status information of the network and devices in real time, and monitor network parameters and device status based on the collected information;

[0007] S2: Generate optimization strategy: Based on the monitoring data provided in S1, evaluate the network load and device importance, and use a weighted scoring model for analysis to generate an optimized reporting strategy;

[0008] S3: Determine whether the target device needs to adjust the policy. If not, keep the existing policy. If necessary, enter S4.

[0009] S4: Policy download and device configuration: Send the generated optimization policy to the target device through the Zigbee gateway, and ensure that the target device updates the configuration correctly so that the new policy takes effect and is applied.

[0010] Preferably, the specific logical steps of S1 are as follows:

[0011] S101: Protocol extension: Based on the Zigbee standard protocol, the customized monitoring instructions and data formats are extended to transmit monitoring information;

[0012] S102: Collecting network parameters: by monitoring the data transmission on the channel, counting the channel occupancy rate per unit time, and calculating the ratio between the sent data packets and the response packets of the successful reception confirmation, calculating the data packet loss rate, and recording the signal strength index of the received data packets, and calculating the average signal strength;

[0013] S103: Collecting device status: Counting the number of device data changes in a unit time, calculating the data change frequency, recording key events of the device, including alarms and faults, calculating the event triggering frequency, and calculating the remaining power of the device through the power information reported by the device and querying the power attributes of the device;

[0014] S104: Storing monitoring data: The data processed in S102 and S103 are stored in the database of the gateway for subsequent analysis.

[0015] Preferably, the specific logical steps of S2 are as follows:

[0016] S201: Acquire the monitoring data in step S1, evaluate the network load and device importance according to the monitoring data, and calculate the network load score and the device importance score;

[0017] S202: Identify devices that require policy adjustment based on the network load score and device importance score calculated in S201;

[0018] S203: Determine a specific reporting policy optimization scheme for the device that needs to adjust the policy, wherein the policy optimization scheme includes adjusting the reporting interval and key parameters of the event triggering condition, and ensuring that the device reporting frequency matches the reasonable allocation of network resources.

[0019] Preferably, in S201, the formula used to calculate the network load score is:

[0020] Network load score = a × channel occupancy + b × packet loss rate + c × (1-average signal strength)

[0021] Among them, a, b, and c are weight coefficients, and the load level is divided according to the calculated network load score: when the score is lower than 30%, it is low load and no policy adjustment is required; when the score is between 30% and 70%, the reporting policy of non-critical equipment needs to be adjusted; when the score is higher than 70%, the policy needs to be adjusted to ensure network stability.

[0022] Preferably, in S201, the formula used to calculate the device importance score is:

[0023] Device importance score = w1×data change frequency+w2×event trigger frequency+w3×(1-battery power / full power)

[0024] Among them, w1, w2, and w3 are weight coefficients, and critical equipment and non-critical equipment are classified according to the calculated equipment importance score: when the equipment importance score is higher than the set threshold, it is a critical device, and its reporting frequency needs to be prioritized; when the equipment importance score is lower than the set threshold, it is a non-critical device, and its reporting frequency can be reduced.

[0025] Preferably, the specific logical steps of S4 are as follows:

[0026] S401: Formulate a unified policy instruction frame to ensure the effective transmission of policy instructions in the Zigbee network and the correct parsing of devices. The policy instruction frame format follows the custom command format of the Zigbee application layer protocol (APS), which includes two parts: a frame header and a payload.

[0027] S402: The Zigbee gateway evaluates the current channel quality, selects the best time to send the policy instruction, and receives the policy instruction through the device. Using the confirmation service of the Zigbee APS layer, the sender waits for the receiver's confirmation frame (ACK) within the specified timeout period. If the confirmation frame (ACK) is not received within the timeout period, the sender retransmits according to the exponential backoff algorithm, and the number of retransmissions is configurable.

[0028] S403: The device parses the received instruction and verifies the validity of the instruction;

[0029] S404: When the instruction verified in S403 is valid, the device reporting policy is updated in the RAM, the policy takes effect immediately, and the device reports data according to the new policy;

[0030] S405: When the command checked in S403 is invalid, the device sends an error report to the Zigbee gateway, and the Zigbee gateway records and processes the error information;

[0031] S406: The device sends status information of the device configuration update to the Zigbee gateway, where the status information includes reasons for success and failure.

[0032] Preferably, in S401, the frame header includes a command identifier, a frame control field and a sequence number, the command identifier is used to identify the instruction type, the frame control field contains the frame type, transmission direction and security, the sequence number is used to track and confirm the instruction, and the payload part contains the address and policy parameters of the target device, the policy parameters include a new reporting interval and event trigger threshold, and a checksum for verifying the integrity of the instruction data.

[0033] Preferably, in S405, when the instruction is invalid, the device should maintain the currently running policy to avoid generating uncertain behavior.

[0034] Preferably, in S404, when updating the device reporting policy, the reporting policy parameters are updated during operation, and the default settings are restored after the device is restarted. When the device is started, the reporting policy parameters are loaded from the preset default configuration to ensure a consistent initial state.

[0035] Compared with the prior art, the present invention has the following beneficial effects:

[0036] The present invention monitors the network and device status in real time, analyzes the network load and device importance, and dynamically generates an optimized reporting strategy, and sends it to the target device for dynamic adjustment. By dynamically adjusting the device reporting strategy, redundant communications in the network are reduced, the channel occupancy rate and the probability of data packet collision are reduced, the reliability and efficiency of data transmission are improved, and efficient utilization of network resources and reduction of device power consumption are achieved. It can adapt to different application scenarios and network environments and has high flexibility and scalability. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 A flowchart of a method for dynamically adjusting a Zigbee device reporting strategy in a complex network environment proposed by the present invention;

[0038] Figure 2 A flowchart of step S1 in a method for dynamically adjusting a Zigbee device reporting strategy in a complex network environment proposed by the present invention;

[0039] Figure 3 A flowchart of step S2 in a method for dynamically adjusting a Zigbee device reporting strategy in a complex network environment proposed by the present invention;

[0040] Figure 4 This is a flowchart of step S4 in a method for dynamically adjusting a Zigbee device reporting strategy in a complex network environment proposed by the present invention. DETAILED DESCRIPTION

[0041] The present invention will be further explained below in conjunction with specific embodiments.

[0042] Example

[0043] Reference Figure 1-4 This embodiment proposes a method for dynamically adjusting a Zigbee device reporting strategy in a complex network environment, including the following steps:

[0044] S1: Network and equipment status monitoring: collect key status information of the network and equipment in real time, and monitor network parameters and equipment status based on the collected information to fully understand the current network operation status and equipment working conditions;

[0045] The specific logical steps are as follows:

[0046] S101: Protocol extension: Based on the Zigbee standard protocol, the customized monitoring instructions and data formats are extended to transmit monitoring information;

[0047] S102: Collecting network parameters: by monitoring the data transmission on the channel, counting the channel occupancy rate per unit time, and calculating the ratio between the sent data packets and the response packets of the successful reception confirmation, calculating the data packet loss rate, and recording the signal strength index of the received data packets, and calculating the average signal strength;

[0048] S103: Collecting device status: Counting the number of device data changes in a unit time, calculating the data change frequency, recording key events of the device, including alarms and faults, calculating the event triggering frequency, and calculating the remaining power of the device through the power information reported by the device and querying the power attributes of the device;

[0049] S104: Storing monitoring data: storing the data processed in S102 and S103 in the database of the gateway for subsequent analysis;

[0050] S2: Generate optimization strategy: Based on the monitoring data provided in S1, evaluate the network load and device importance, and use a weighted scoring model for analysis to generate an optimized reporting strategy;

[0051] The specific logical steps are as follows:

[0052] S201: Acquire the monitoring data in step S1, evaluate the network load and device importance according to the monitoring data, and calculate the network load score and the device importance score;

[0053] The formula used to calculate the network load score is:

[0054] Network load score = a × channel occupancy + b × packet loss rate + c × (1-average signal strength)

[0055] Where a, b, and c are weight coefficients, and the load level is divided according to the calculated network load score: when the score is less than 30%, it is a low load and no policy adjustment is required; when the score is between 30% and 70%, the reporting policy of non-critical devices needs to be adjusted; when the score is higher than 70%, the policy needs to be adjusted to ensure network stability;

[0056] The formula used to calculate the device importance score is:

[0057] Device importance score = w1×data change frequency+w2×event trigger frequency+w3×(1-battery power / full power)

[0058] Among them, w1, w2, and w3 are weight coefficients, and the key equipment and non-key equipment are classified according to the calculated equipment importance score: when the equipment importance score is higher than the set threshold, it is a key equipment, and its reporting frequency needs to be prioritized; when the equipment importance score is lower than the set threshold, it is a non-key equipment, and its reporting frequency can be reduced;

[0059] S202: Identify devices that require policy adjustment based on the network load score and device importance score calculated in S201;

[0060] S203: Determine a specific reporting strategy optimization plan for the device that needs to adjust the strategy, wherein the strategy optimization plan includes adjusting the reporting interval and key parameters of the event triggering condition, and ensuring that the device reporting frequency matches the reasonable allocation of network resources;

[0061] S3: Determine whether the target device needs to adjust the policy. If not, keep the existing policy. If necessary, enter S4.

[0062] S4: Policy issuance and device configuration: Send the generated optimization policy to the target device through the Zigbee gateway, and ensure that the target device updates the configuration correctly so that the new policy takes effect and is applied. Through the issuance of policies and the update of device configuration, the entire network can dynamically adapt to the current network load and device status to achieve efficient use of resources;

[0063] The specific logical steps are as follows:

[0064] S401: Formulate a unified policy instruction frame to ensure the effective transmission of policy instructions in the Zigbee network and the correct parsing of devices. The policy instruction frame format follows the custom command format of the Zigbee application layer protocol (APS), which includes two parts: a frame header and a payload.

[0065] The frame header includes a command identifier, a frame control field, and a sequence number. The command identifier is used to identify the instruction type. For example, `0xA1` indicates a report policy adjustment instruction. The frame control field contains the frame type, transmission direction, and security. The sequence number is used to track and confirm the instruction. The payload contains the address and policy parameters of the target device. The policy parameters include a new reporting interval and event trigger threshold, as well as a checksum used to verify the integrity of the instruction data.

[0066] The specific instruction data frame structure is as follows:

[0067]

[0068]

[0069] S402: The Zigbee gateway evaluates the current channel quality, selects the best time to send the policy instruction, and receives the policy instruction through the device. Using the confirmation service of the Zigbee APS layer, the sender waits for the receiver's confirmation frame (ACK) within the specified timeout period. When the confirmation frame (ACK) is not received within the timeout period, the sender retransmits according to the exponential backoff algorithm. The number of retransmissions is configurable, for example, up to 3 times. At the same time, the Zigbee gateway manages the serial number before sending the instruction and filters the repeated instructions. Through the management of the serial number and the filtering of the repeated instructions, the uniqueness of the instruction is ensured to prevent repeated execution or omission.

[0070] S403: The device parses the received instruction and verifies the validity of the instruction;

[0071] S404: When the instruction verified in S403 is valid, the device reporting policy is updated in the RAM, and the policy takes effect immediately. The device reports data according to the new policy, and the new policy parameters take effect only in the RAM, ensuring the real-time nature of the policy.

[0072] When updating the device reporting policy, the reporting policy parameters are updated during operation and restored to the default settings after the device is restarted. When the device starts, it loads the reporting policy parameters from the preset default configuration to ensure a consistent initial state;

[0073] S405: When the command checked in S403 is invalid, the device sends an error report to the Zigbee gateway, and the Zigbee gateway records and processes the error information. When the command is invalid, the device should maintain the current running strategy to avoid uncertain behavior;

[0074] S406: The device sends the status information of the device configuration update to the Zigbee gateway, and the status information includes the reasons for success and failure, so that the Zigbee gateway can perform corresponding processing;

[0075] This embodiment monitors the network and device status in real time, analyzes the network load and device importance, and dynamically generates an optimized reporting strategy, and sends it to the target device for dynamic adjustment. By dynamically adjusting the device reporting strategy, redundant communications in the network are reduced, channel occupancy and packet collision probability are reduced, and the reliability and efficiency of data transmission are improved. Efficient use of network resources and reduction of device power consumption are achieved. It can adapt to different application scenarios and network environments and has high flexibility and scalability.

[0076] The above description is only a preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can make equivalent replacements or changes according to the technical scheme and inventive concept of the present invention within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.

Claims

1. A method for dynamically adjusting a Zigbee device reporting strategy in a complex network environment, characterized in that: The following steps are involved: S1: Network and device status monitoring: collect key status information of the network and devices in real time, and monitor network parameters and device status based on the collected information; S2: Generate optimization strategy: Based on the monitoring data provided in S1, evaluate the network load and device importance, and use a weighted scoring model for analysis to generate an optimized reporting strategy; S3: Determine whether the target device needs to adjust the policy. If not, keep the existing policy. If necessary, enter S4. S4: Policy download and device configuration: Send the generated optimization policy to the target device through the Zigbee gateway, and ensure that the target device updates the configuration correctly so that the new policy takes effect and is applied.

2. A method for dynamically adjusting Zigbee device reporting strategy in a complex network environment according to claim 1, characterized in that: The specific logical steps of S1 are as follows: S101: Protocol extension: Based on the Zigbee standard protocol, the customized monitoring instructions and data formats are extended to transmit monitoring information; S102: Collecting network parameters: by monitoring the data transmission on the channel, counting the channel occupancy rate per unit time, and calculating the ratio between the sent data packets and the response packets of the successful reception confirmation, calculating the data packet loss rate, and recording the signal strength index of the received data packets, and calculating the average signal strength; S103: Collecting device status: Counting the number of device data changes in a unit time, calculating the data change frequency, recording key events of the device, including alarms and faults, calculating the event triggering frequency, and calculating the remaining power of the device through the power information reported by the device and querying the power attributes of the device; S104: Storing monitoring data: The data processed in S102 and S103 are stored in the database of the gateway for subsequent analysis.

3. A method for dynamically adjusting Zigbee device reporting strategy in a complex network environment according to claim 2, characterized in that: The specific logical steps of S2 are as follows: S201: Acquire the monitoring data in step S1, evaluate the network load and device importance according to the monitoring data, and calculate the network load score and the device importance score; S202: Identify devices that require policy adjustment based on the network load score and device importance score calculated in S201; S203: Determine a specific reporting policy optimization scheme for the device that needs to adjust the policy, wherein the policy optimization scheme includes adjusting the reporting interval and key parameters of the event triggering condition, and ensuring that the device reporting frequency matches the reasonable allocation of network resources.

4. A method for dynamically adjusting Zigbee device reporting strategy in a complex network environment according to claim 3, characterized in that: In S201, the formula used to calculate the network load score is: Network load score = a × channel occupancy + b × packet loss rate + c × (1-average signal strength) Among them, a, b, and c are weight coefficients, and the load level is divided according to the calculated network load score: if the score is lower than 30%, it is low load and no policy adjustment is required; if the score is between 30% and 70%, the reporting policy of non-critical equipment needs to be adjusted; if the score is higher than 70%, the policy needs to be adjusted to ensure network stability.

5. The method for dynamically adjusting the Zigbee device reporting strategy in a complex network environment according to claim 3, characterized in that: In S201, the formula used to calculate the device importance score is: Device importance score = w1×data change frequency+w2×event trigger frequency+w3×(1-battery power / full power) Among them, w1, w2, and w3 are weight coefficients, and critical equipment and non-critical equipment are classified according to the calculated equipment importance score: if the equipment importance score is higher than the set threshold, it is a critical device, and its reporting frequency needs to be prioritized; if the equipment importance score is lower than the set threshold, it is a non-critical device, and its reporting frequency can be reduced.

6. A method for dynamically adjusting Zigbee device reporting strategy in a complex network environment according to claim 1, characterized in that: The specific logical steps of S4 are as follows: S401: Formulate a unified policy instruction frame to ensure the effective transmission of policy instructions in the Zigbee network and the correct parsing of devices. The policy instruction frame format follows the custom command format of the Zigbee application layer protocol (APS), which includes two parts: a frame header and a payload. S402: The Zigbee gateway evaluates the current channel quality, selects the best time to send the policy instruction, and receives the policy instruction through the device. Using the confirmation service of the Zigbee APS layer, the sender waits for the receiver's confirmation frame (ACK) within the specified timeout period. If the confirmation frame (ACK) is not received within the timeout period, the sender retransmits according to the exponential backoff algorithm, and the number of retransmissions is configurable. S403: The device parses the received instruction and verifies the validity of the instruction; S404: If the instruction verified in S403 is valid, the device reporting policy is updated in the RAM, the policy takes effect immediately, and the device reports data according to the new policy; S405: If the command checked in S403 is invalid, the device sends an error report to the Zigbee gateway, and the Zigbee gateway records and processes the error information; S406: The device sends status information of the device configuration update to the Zigbee gateway, where the status information includes reasons for success and failure.

7. A method for dynamically adjusting Zigbee device reporting strategy in a complex network environment according to claim 6, characterized in that: In S401, the frame header includes a command identifier, a frame control field and a sequence number. The command identifier is used to identify the instruction type. The frame control field contains the frame type, transmission direction and security. The sequence number is used to track and confirm the instruction. The payload part contains the address and policy parameters of the target device. The policy parameters include a new reporting interval and event trigger threshold, as well as a checksum for verifying the integrity of the instruction data.

8. A method for dynamically adjusting Zigbee device reporting strategy in a complex network environment according to claim 6, characterized in that: In S405, when the instruction is invalid, the device should maintain the currently running strategy to avoid generating uncertain behavior.

9. A method for dynamically adjusting Zigbee device reporting strategy in a complex network environment according to claim 6, characterized in that: In S404, when updating the device reporting policy, the reporting policy parameters are updated during operation, and the default settings are restored after the device is restarted. When the device is started, the reporting policy parameters are loaded from the preset default configuration to ensure a consistent initial state.

Images