A landscape light zoning linkage control method

Abstract

The application relates to the technical field of light linkage control and discloses a landscape light partition linkage control method, which comprises the following steps: through auxiliary verification upgrading to a causal determination core mechanism by time intervention experiment, precise decision of network domain and clock domain root causes is realized; through a three-layer progressive diagnosis architecture, layer-by-layer decoupling and locking of misjudgment of communication time delay jitter, network congestion and clock drift accumulation are realized; through link quality-concurrent load double-dimensional isolation tracing and topological distance gradient attenuation analysis, fine differentiation of network domain root causes is realized; through a differentiated repair strategy and a time intervention closed-loop verification, instant confirmation of repair effect and adaptive reset of the diagnosis process are realized; and finally, the fault diagnosis accuracy, repair efficiency and system operation stability of the landscape light partition linkage control are improved.

Description

Technical Field

[0001] This invention relates to the field of lighting linkage control technology, specifically a method for zonal linkage control of landscape lighting. Background Technology

[0002] In large-scale landscape lighting systems, a zoned linkage control method is typically used to uniformly schedule lights in different areas to achieve a consistent overall lighting effect. However, in actual operation, factors such as differences in network topology between zones, fluctuations in communication link quality, and changes in the load of concurrent control commands can easily lead to time delay deviations in the transmission of control commands between zones, resulting in problems such as asynchronous light execution, brightness deviations, and distortion of linkage rhythm. Existing methods for zoned linkage control of landscape lighting lack diagnostic means to isolate clock drift accumulation from network transmission latency jitter at the domain level. This leads to the root cause remaining unresolved when the symptoms of the two are highly overlapping. The lack of a two-dimensional decoupling mechanism between link quality-sensitive components and concurrent load-sensitive components makes it easy to misjudge as a single factor or to repeatedly jump between them. The lack of a causal determination mechanism centered on proactive intervention makes it impossible to distinguish between chronic congestion and clock drift. The lack of a closed-loop verification system anchored by time-based intervention makes it impossible to confirm whether the root cause has been truly eliminated after repair, resulting in repeated failures. Its practicality has certain limitations. Summary of the Invention

[0003] This invention provides a method for coordinated control of landscape lighting zones. It establishes a clock synchronization reference baseline by constructing a bidirectional communication delay benchmark under low load conditions. The bidirectional delay difference is calculated by combining the control command sending and receiving times. Network topology hop count and system concurrent load status parameters are introduced to perform correlation analysis and classification of delay anomalies. Simultaneously, environmental disturbance parameters and link communication quality parameters are combined to distinguish the sources of anomalies. Independent time calibration is performed when a clock offset exceeds a preset synchronization threshold. Finally, the zoned lighting coordinated control strategy is adjusted based on the delay offset type and clock calibration results, thereby achieving stable and coordinated control of multi-zone lighting systems. This method improves the accuracy of zoned communication delay anomaly identification, enhances the synchronization of multi-zone coordinated execution, and improves clock calibration stability. It solves the problems mentioned in the background art, such as the difficulty in accurately identifying zoned delay anomalies, the difficulty in distinguishing anomaly sources, and the asynchrony of zoned lighting coordinated control caused by network topology differences, communication link quality fluctuations, and changes in concurrent control load in multi-zone landscape lighting systems.

[0004] This invention provides the following technical solution: a method for zoned linkage control of landscape lighting, comprising: Under low load conditions, the bidirectional communication delay between each partition and the central controller is collected to establish the partition topology and the reference propagation delay. Periodically measure the outbound and return delays, and calculate the bidirectional delay deviation sequence; Based on the differences between the brightness feedback of each partition and the target brightness, as well as the linkage timing deviation, a consistent linkage execution result is generated. The load and response distribution of concurrent commands from the centralized controller are collected to obtain load status parameters; Based on bidirectional latency deviation, load status, and topology hop count, a preliminary attribution analysis is performed on partition latency anomalies. The consistency of the preliminary attribution results was verified by combining environmental disturbance information to distinguish between environmental impacts and link factors; When a clock synchronization offset exceeding the threshold is detected, a unified clock calibration command is sent to each partition through an independent time synchronization intervention channel. Based on the time delay changes before and after calibration, the communication anomaly type is determined and the corresponding lighting zone linkage control strategy is output.

[0005] Preferably, the partition node identifier, the link connection relationship between nodes and the network topology hop count information are obtained, and when the central controller is in a preset low service load window, the sending time and receipt time of each partition control command are recorded respectively, and the average bidirectional communication delay is calculated as the reference value for clock synchronization of each partition.

[0006] Preferably, for the same control command, the sending timestamp and the receiving timestamp are recorded respectively, the outbound delay and the return delay are calculated, and the outbound delay and the return delay are successively calculated to obtain a bidirectional delay difference sequence of multiple samples.

[0007] Preferably, the brightness feedback values ​​of each zone are collected within a preset time window and compared with the target brightness setting value point by point. At the same time, the sending time of the corresponding control command and the response time when the brightness feedback reaches a stable value are recorded, and the brightness deviation value and response time deviation value are calculated.

[0008] Preferably, the number of control commands sent by the central controller, the time interval between adjacent command sending, and the distribution dispersion of the receipt arrival time of each partition are counted within a unit of time, and these three are used as components of the system concurrent load status parameters.

[0009] Preferably, the bidirectional delay difference sequence, network topology hop count information and system concurrent load status parameters are matched partition by partition, and each partition is classified according to a preset delay offset classification threshold to obtain the partition delay offset type.

[0010] Preferably, the temperature change, humidity change, and external light change parameters in the environmental disturbance parameters are collected, and the packet loss rate and link delay jitter value in the link communication quality parameters are collected. These parameters are then compared with the delay anomaly data in the same time window to determine the anomaly source category.

[0011] Preferably, when the local clock offset of each partition is detected to exceed the preset synchronization threshold, a unified clock calibration command is sent to each partition through an independent time synchronization communication link, and the local clock reference value of each partition is re-recorded as the update reference after calibration.

[0012] Preferably, lighting linkage control adjustment commands are generated according to the partition delay offset type and clock calibration results, including adjusting the partition execution timing or adjusting the partition synchronization cycle, so as to achieve linkage synchronization control between partitions.

[0013] The present invention has the following beneficial effects: 1. This landscape lighting zone linkage control method divides the landscape area into several independent control zones based on differences in functional attributes, physical boundaries, and lighting requirements. A global spatial topology network is established, and multi-source sensing nodes are deployed in each zone to construct a heterogeneous sensing system. At the same time, a wireless communication network consisting of a centralized gateway, multi-hop relay nodes, and zone controllers is built. Link quality monitoring fields are embedded in the communication frames, a network topology mapping table is established, and historical baseline propagation delay is calibrated. A concurrent load monitoring channel and an independent time-based intervention command channel are established to provide underlying hardware and data support for subsequent diagnosis and repair. Through zoned topology modeling and multi-source sensing deployment, full coverage and real-time status monitoring of the landscape space are achieved. Through the pre-configuration of the communication network architecture and monitoring channels, a traceable data foundation and triggerable intervention channels are provided for the root cause diagnosis of linkage failure.

[0014] 2. This landscape lighting zone linkage control method uses bidirectional delay symmetry analysis and a first time-intervention experiment to complete the initial screening of domain isolation between the network domain and the clock domain. It extracts the link quality sensitivity index and concurrent load sensitivity index and performs topological distance gradient analysis. Combined with time-intervention baseline purification, it completes the detailed locking of communication delay jitter and network congestion within the network domain. Through stepped concurrent stress testing, long-cycle delay tracking, and a second time-intervention experiment, it completes the final decoupling of network congestion pulse components and clock drift accumulation components. The time-intervention experiment runs through all levels and serves as the core mechanism for causal determination. Through a three-layer progressive architecture and the core mechanism of causal determination of the time-intervention experiment, it achieves accurate decoupling and root cause locking of misjudgments of communication delay jitter, network congestion, and clock drift accumulation, avoiding ineffective repair investment.

[0015] 3. This landscape lighting zone linkage control method, based on the root cause diagnosis conclusion, matches and executes clock domain repair, link quality repair, concurrent load repair, or combined repair strategies. After the repair is completed, a third time-intervention experiment is conducted to verify whether the end-to-end latency of each zone has returned to the baseline value and whether the linkage synchronization failure has been eliminated. If the closed-loop verification passes, the repair process terminates. If it fails, the current latency data is used as a new manifestation feature, and the progressive diagnosis is restarted, forming an adaptive closed-loop verification system with time-intervention as the anchor point. Through root cause-oriented differentiated repair and time-intervention closed-loop verification, the precise matching of repair strategies and the immediate confirmation of repair effects are achieved. Through the adaptive diagnostic reset mechanism, the continuous and stable operation of the system is ensured.

[0016] 4. This landscape lighting zone linkage control method improves the stability and consistency of the zone clock reference by constructing a clock synchronization reference baseline under low load conditions. It enhances the precision of delay anomaly identification by introducing bidirectional delay difference values ​​and topology hop count information. By combining concurrent load state parameters, it effectively characterizes the impact of system load fluctuations on delay. By distinguishing between environmental factors and link factors, it improves the accuracy of determining the root cause of communication anomalies. Through clock calibration and linkage control strategy adjustment, it improves the synchronization and stability of zone lighting linkage control. Attached Figure Description

[0017] Figure 1 This is a flowchart of the landscape lighting zone linkage control method of the present invention; Figure 2 This is a structural diagram of the landscape lighting zone linkage control system of the present invention; Figure 3 This is a schematic diagram illustrating the calculation of the bidirectional time delay difference value according to the present invention; Figure 4 This is a schematic diagram of the network topology hop count grouping of the present invention. Detailed Implementation

[0018] Example 1: A method for coordinated control of landscape lighting zones, comprising: Under low load conditions, the bidirectional communication delay between each partition and the central controller is collected to establish the partition topology and the reference propagation delay. Periodically measure the outbound and return delays, and calculate the bidirectional delay deviation sequence; Based on the differences between the brightness feedback of each partition and the target brightness, as well as the linkage timing deviation, a consistent linkage execution result is generated. The load and response distribution of concurrent commands from the centralized controller are collected to obtain load status parameters; Based on bidirectional latency deviation, load status, and topology hop count, a preliminary attribution analysis is performed on partition latency anomalies. The consistency of the preliminary attribution results was verified by combining environmental disturbance information to distinguish between environmental impacts and link factors; When a clock synchronization offset exceeding the threshold is detected, a unified clock calibration command is sent to each partition through an independent time synchronization intervention channel. Based on the time delay changes before and after calibration, the communication anomaly type is determined and the corresponding lighting zone linkage control strategy is output.

[0019] Example 2 is an improvement upon Example 1. This landscape lighting zone linkage control method establishes a zone topology and a reference propagation delay, specifically as follows: Obtain the basic attribute dataset of the landscape zoning of the target landscape area. The basic attribute dataset of the landscape zoning includes topographic data, functional attribute labels, physical boundary coordinates and light demand level. Topographic data refers to the spatial basic data describing the topographic relief, geomorphic features and elevation distribution of the landscape area. Functional attribute labels refer to the classification labels that identify the functional categories of the zoning (such as trail area, water area, building facade area, vegetation area). Physical boundary coordinates refer to the set of geographic coordinate points that define the spatial range of each zoning. Light demand level refers to the level parameters that characterize the lighting brightness, color temperature and dynamic change requirements of each zoning. The landscape area is divided into several independent control zones based on functional attribute labels, and a unique identifier is assigned to each zone. Establish an adjacency table for adjacent partitions based on physical boundary coordinates; Establish a cross-zone linkage priority index based on the level of illumination demand; This data is aggregated to form a global spatial topology network. Acquire the spatial coordinates of the planned deployment locations of each zone, the sensing radius of each type of sensor, and the obstacle distribution data within the zone. The obstacle distribution data refers to the spatial location and geometric range of obstacles such as structures, trees, and terrain undulations that obstruct the sensing signal within the zone. For any spatial point within the partition, perform a completeness verification of the perception coverage: If the distance from the spatial point to the deployment location of at least one sensing node is less than or equal to the sensing radius of the sensing node, and there are no obstacles separating the spatial point and the sensing node, then the spatial point is determined to be an effective sensing coverage point. The sensing node refers to the sensor entity deployed in each partition and its installation location coordinates. If the distance from the spatial point to the deployment location of all sensing nodes is greater than the sensing radius of the corresponding sensing node, or if there are obstacles separating the spatial point from all sensing nodes, then the spatial point is determined to be a sensing blind spot. If there are blind spots in perception, add perception nodes in the blind spots or adjust the deployment positions of existing perception nodes until all perception blind spots are eliminated. If there are no blind spots in perception, then the deployment of the current multi-source perception system is confirmed to be complete; Obtain the communication network hardware capability parameter set, which includes the communication interface type of each partition controller, the concurrent processing capacity of the central gateway, and the maximum forwarding hop count of multi-hop relay nodes. The communication interface type of each partition controller refers to the wireless or wired communication protocol and physical interface specifications supported by the partition controller. The concurrent processing capacity of the central gateway refers to the maximum number of instructions that the central gateway can receive, process, and forward simultaneously per unit time. The maximum forwarding hop count of multi-hop relay nodes refers to the upper limit of the data forwarding layer allowed by the relay node in the network architecture. Multi-hop relay nodes refer to intermediate forwarding devices deployed between the central gateway and remote partition controllers in the wireless communication network, used to relay data packets segment by segment to extend the communication coverage and overcome signal attenuation caused by physical obstruction. Construct a wireless communication network consisting of a centralized gateway, multi-hop relay nodes, and a partition controller; A link quality monitoring indication structure is formed by embedding a transmission timestamp field, a reception timestamp field, a signal strength indicator field, a signal-to-noise ratio indicator field, and a retransmission count field into a regular communication frame. Here, a regular communication frame refers to a standard data packet containing control commands and status data that is periodically transmitted in the system. The signal strength indicator field is a monitoring field embedded in the communication frame to characterize the level of wireless signal reception power. The signal-to-noise ratio indicator field is a monitoring field embedded in the communication frame to characterize the ratio of signal power to background noise power. The retransmission count field is a monitoring field embedded in the communication frame to record the number of times a data packet is repeatedly transmitted due to transmission failure. Obtain the network link transmission characteristic parameter set from each partition controller to the central gateway. The network link transmission characteristic parameter set includes the physical connection path, the nominal bandwidth of each link segment, and the forwarding delay of each hop relay node. The physical connection path refers to the physical link route through which the signal transmission between the partition controller and the central gateway passes. The nominal bandwidth of each link segment refers to the data transmission rate of each link segment in the physical connection path under standard conditions. The forwarding delay of each hop relay node refers to the processing and queuing time generated when the data packet passes through each hop relay node. If there is a direct physical connection path between a certain partition controller and the central gateway, then the partition is determined to be a directly connected partition, and its hop count is recorded as one. If a partition controller and the central gateway need to forward data via a relay node, then the partition is determined to be a relay partition, and its hop count is recorded as the number of relay nodes plus one. Establish a network topology mapping table to record the network topology attribute records of each partition. The partition network topology attribute records include a unique identifier, hop count, nominal bandwidth of each link segment, and historical baseline propagation delay. The unique identifier is a non-repeatable identification code used to distinguish different partitions. The hop count is the number of relay nodes traversed by the data forwarding between the partition controller and the central gateway plus one. The nominal bandwidth of each link segment is the standard data transmission rate of each link segment recorded in the network topology mapping table. The historical baseline propagation delay is the one-way signal propagation time from the partition to the gateway measured under low system load conditions. Under low system load conditions, send reference probe frames to each partition and record round-trip latency; Half of the measured round-trip time is written into the network topology mapping table as the historical baseline propagation time for that partition; Obtain the configuration parameter set for the concurrent load monitoring channel. The configuration parameter set includes the maximum depth of the central gateway's sending queue, the peak frequency of instruction issuance per unit time, and the timeout threshold for response receipts of each partition. The maximum depth of the central gateway's sending queue refers to the upper limit of the number of instructions to be sent that the central gateway's sending buffer can hold. The peak frequency of instruction issuance per unit time refers to the maximum number of instructions that the central gateway can send to all partitions in one second. The timeout threshold for response receipts of each partition refers to the maximum time interval allowed from the issuance of an instruction to the receipt of the corresponding receipt. A concurrent load monitoring channel is established on the centralized controller side to record the concurrent load real-time monitoring dataset per unit time, forming a concurrent load monitoring dataset. The concurrent load real-time monitoring dataset includes the total number of instructions issued, the current depth of the gateway sending queue, and the arrival time distribution of response receipts from each partition. The total number of instructions issued refers to the total number of instructions sent by the centralized gateway to each partition within the statistical time window. The current depth of the gateway sending queue refers to the number of instructions that have not yet been sent in the centralized gateway sending buffer at a certain moment. The arrival time distribution of response receipts from each partition refers to the time sequence of each partition's receipts arriving at the centralized gateway and its discrete characteristics. The system reserves an independent time-synchronization intervention command channel. The commands in this channel have a higher priority than regular communication frames, ensuring that the time-synchronization intervention experiment can be safely triggered at any diagnostic stage, and providing hardware-level support for subsequent causal determination.

[0020] Example 3 is an improvement on Example 2. In this example, the outbound and return delays are periodically measured, and the bidirectional delay deviation sequence is calculated. Specifically: The linkage out-of-synchronization detection parameter set of each zone's lighting execution terminal is obtained. The linkage out-of-synchronization detection parameter set includes the actual brightness feedback value, the target brightness setting value, the lighting state switching timing tolerance threshold, and the current linkage cycle number. The actual brightness feedback value refers to the measured luminous flux or relative brightness value returned by the brightness sensor to the central controller after the lighting execution terminal receives the dimming command. The target brightness setting value refers to the theoretical brightness requirement value calculated and issued by the system for each zone based on the current scene mode. The lighting state switching timing tolerance threshold refers to the maximum time deviation between the actual state switching time of each zone and the standard timing reference. The current linkage cycle number refers to the sequence number that identifies a complete linkage control cycle. For any given linkage cycle, the following steps are triggered: linkage synchronization failure determination and initial domain isolation screening: If the deviation between the actual brightness feedback value and the target brightness setting value of at least one zone exceeds the brightness tolerance threshold, and the deviation between the state switching time of the zone and the standard timing reference exceeds the timing tolerance threshold, then the zone is determined to have a linkage failure. The brightness tolerance threshold refers to the maximum deviation between the actual brightness feedback value and the target brightness setting value that is allowed to determine whether the actual output of the lamp meets the standard. The timing tolerance threshold is the lighting state switching timing tolerance threshold. If the deviation between the actual brightness feedback value and the target brightness setting value of all partitions in all linkage cycles does not exceed the brightness tolerance threshold, and the deviation between the state switching time of all partitions and the standard timing reference does not exceed the timing tolerance threshold, then it is determined that the current system has not experienced linkage synchronization failure, and there is no need to start domain isolation initial screening. If a synchronization failure is detected, the domain isolation initial screening process is triggered. Acquire the transmission time records of probe frames sent by the gateway to each partition controller, the reception time records of probe frames received by each partition controller, the transmission time records of response frames sent back by each partition controller, and the final arrival time records of response frames received by the gateway. Based on the transmission time record and the reception time record, the outbound propagation delay of the signal from the gateway to the partition controller is determined. That is, the time difference is calculated by the transmission time record of the gateway sending the probe frame and the reception time record of the partition controller receiving the probe frame, and the propagation time of the signal on the one-way transmission path from the gateway to the partition controller is obtained. Based on the return time record and the final arrival time record, the return propagation delay of the signal from the partition controller to the gateway is determined. That is, the time difference is calculated between the return time record of the response frame sent by the partition controller and the final arrival time record of the response frame received by the gateway to obtain the propagation time of the signal on the one-way transmission path from the partition controller to the gateway. The outbound propagation delay and the return propagation delay are associated with the corresponding partition and linkage cycle number to form a single-cycle bidirectional delay record. The linkage cycle number refers to a unique sequence identifier assigned to each complete lighting linkage control cycle in chronological order. Obtain single-cycle bidirectional delay records for multiple consecutive linkage cycles to obtain the difference sequence between the outbound propagation delay and the return propagation delay of each partition. That is, extract the outbound propagation delay and the return propagation delay of the same partition from multiple consecutive linkage cycles, calculate the difference between the two cycles one by one, and arrange the difference of each cycle in the order of linkage cycle number to form the bidirectional delay difference sequence of the partition. Analyze the distribution characteristics of this difference sequence: If each difference in the difference sequence exhibits irregular positive and negative fluctuations near zero, and the dispersion of the difference fluctuations exceeds a preset fluctuation threshold, then the bidirectional time delay asymmetry of the partition is determined to exhibit a random high variance distribution. If each difference in the difference sequence is stably distributed around a fixed non-zero value, and the dispersion of the difference fluctuation does not exceed the preset fluctuation threshold, then the bidirectional time delay asymmetry of the partition is determined to be close to a fixed offset. If the difference sequence does not exhibit a random high variance distribution or a fixed offset distribution, then the bidirectional time delay asymmetry characteristic of the partition is determined to be atypical. The environmental disturbance monitoring parameter set of each partition during the transmission of the detection frame is acquired to form a time-series record of environmental variables. The environmental disturbance monitoring parameter set includes rain and snow intensity monitoring values, environmental temperature and humidity monitoring values, obstruction status indicators, and human flow density monitoring values. Rain and snow intensity monitoring values ​​refer to the quantified values ​​of precipitation intensity measured by meteorological sensors. Environmental temperature and humidity monitoring values ​​refer to the environmental temperature and relative humidity readings measured by temperature and humidity sensors. Obstruction status indicators refer to the marking data that characterizes whether there are signal obstructions and their spatial locations between the sensing node and the partition controller. Human flow density monitoring values ​​refer to the number of people per unit area measured by human flow detection sensors. The outbound and return propagation delay sequences of each partition are correlated and compared with the environmental variable time series records. The outbound propagation delay sequence refers to the time series data formed by arranging the outbound propagation delay of the signal from the gateway to the partition controller measured in multiple consecutive linkage cycles of the same partition, in the order of the linkage cycle number. The return propagation delay sequence refers to the time series data formed by arranging the return propagation delay of the signal from the partition controller to the gateway measured in multiple consecutive linkage cycles of the same partition, in the order of the linkage cycle number. If the peak time in the time delay sequence coincides with the start time of severe weather, the time of increase of obstruction, or the peak time of human flow in the environmental variable time series record, and the time delay sequence monotonically increases as the environmental variable worsens and monotonically decreases as the environmental variable improves, then it is determined that there is a significant correlation between the time delay sequence of this partition and the environmental disturbance. If the peak moment in the time delay sequence does not overlap with the extreme environmental event moment in the environmental variable time series record, and the changing trend of the time delay sequence is independent of the changing trend of the environmental variable, then it is determined that the time delay sequence of this partition is basically unrelated to the environmental disturbance. If both of the above conditions are partially met, it is determined that there is a weak correlation between the time delay sequence of the partition and the environmental disturbance. Based on the combined characteristics of bidirectional delay asymmetry and the results of the delay environment correlation assessment, a preliminary domain isolation screening and direction determination is performed: If the bidirectional delay asymmetry exhibits a random high variance distribution, and there is a significant correlation between the delay sequence and environmental disturbances, then the apparent characteristics initially point to communication delay jitter. If the bidirectional delay asymmetry approaches a fixed offset and the delay sequence is basically uncorrelated with environmental disturbances, then the apparent characteristics initially point to clock drift accumulation. If the bidirectional delay asymmetry characteristics are not typical, or if there is only a weak correlation between the delay sequence and environmental disturbances, then it is determined that the apparent characteristics do not clearly point to a single domain, and the suspected clock drift marker is retained while the suspected network domain marker is recorded synchronously.

[0021] This embodiment also provides the generation of consistent execution results, specifically: The system acquires the following information: the feature acquisition completion flag, the current status flag of the time synchronization intervention command channel, and the standard clock source timestamp. The feature acquisition completion flag indicates the status flag output after periodically measuring outbound and return delays, calculating the bidirectional delay deviation sequence, completing bidirectional delay symmetry analysis, environmental variable correlation comparison, and initial domain isolation screening. When this flag is valid, it indicates that the periodic measurement of outbound and return delays and the calculation of the bidirectional delay deviation sequence have generated complete feature acquisition results. The current status flag of the time synchronization intervention command channel indicates the real-time occupancy status of the independent time synchronization intervention command channel reserved for establishing partition topology and reference propagation delay. When this flag is idle, it indicates that the channel is not occupied by other diagnostic tasks or maintenance operations, and the conditions for issuing a forced time synchronization command are met. The standard clock source timestamp refers to the current precise reference time value from the system time synchronization module or network time protocol server, serving as the calibration target time carried in the forced time synchronization command for uniformly correcting the local clocks of each partition controller. If the appearance feature acquisition is completed and the current status of the time synchronization intervention command channel is idle, then the time synchronization intervention trigger condition is met. A forced time synchronization command is sent to all partition controllers through an independent time synchronization intervention command channel. The forced time synchronization command carries the standard clock source timestamp. If the feature acquisition completion flag is invalid, or the current status flag of the time-synchronization intervention command channel is occupied, it is determined that the time-synchronization intervention triggering condition is not met, and the sending operation will be performed after both flags are met simultaneously. Acquire the local clock readings before and after adjustment for each zone controller after receiving the forced time synchronization command, and perform zone local clock calibration and collect calibration confirmation receipts: Each zone controller corrects the local clock reading before adjustment to the reference time corresponding to the standard clock source timestamp based on the standard clock source timestamp in the forced time synchronization command, generates the local clock reading after adjustment, and returns a calibration confirmation receipt to the central controller. The central controller receives calibration confirmation receipts from each zone controller and records the adjusted readings of the local clocks for each zone. After the time synchronization intervention is completed, the arrival time of the calibration confirmation receipt of each partition controller, the measured end-to-end delay of each partition, and the historical reference propagation delay for establishing partition topology and reference propagation delay records are obtained. The measured end-to-end delay of each partition refers to half of the complete round-trip propagation time of the signal from the gateway to the response frame returned to the gateway after the time synchronization intervention is completed, which is the actual propagation time measurement value on the one-way transmission path. The measured end-to-end delay values ​​for each partition are compared with the corresponding historical baseline propagation delays to obtain the delay deviation for each partition: If the measured end-to-end delay is greater than the historical reference propagation delay, then the delay deviation of this partition is the positive value obtained by subtracting the historical reference propagation delay from the measured end-to-end delay. If the measured end-to-end delay is less than or equal to the historical reference propagation delay, then the delay deviation of the partition is the difference between the historical reference propagation delay and the measured end-to-end delay, or it is zero. Obtain the latency deviation of each partition, the latency recovery judgment threshold, and the total number of system partitions. The latency recovery judgment threshold refers to the maximum allowable deviation for determining whether the latency of a partition has returned to normal. The total number of system partitions refers to the total number of independent control partitions after the landscape area is divided. For the latency deviation of each partition, compare the latency deviation with the latency recovery judgment threshold: If the delay deviation is less than or equal to the delay recovery judgment threshold, then the delay of the partition is determined to have been recovered. If the delay deviation is greater than the delay recovery judgment threshold, then the delay of that partition is determined to have not been recovered. The number of partitions whose latency has been recovered; If the number of partitions whose latency has been recovered is equal to the total number of system partitions, then it is determined that the end-to-end latency of each partition immediately returns to the historical reference propagation latency, the out-of-synchronization phenomenon completely disappears, the root cause of the cause is locked as clock drift accumulation, the clock drift accumulation judgment conclusion is directly output, the communication anomaly type is judged and the corresponding lighting partition linkage control strategy is output. If the number of partitions whose latency has been recovered is zero, it is determined that there is no significant change in the end-to-end latency of each partition, the out-of-synchronization phenomenon still exists, the clock domain is excluded as the cause, the problem is confirmed to belong to the network domain, the adjusted local clock reading of each partition is used as the clean clock baseline, and the concurrent command load and receipt distribution of the acquisition central controller are carried with the clean clock baseline and the network domain attribution mark. If the number of partitions whose latency has been recovered is greater than zero and less than the total number of system partitions, it is determined that the end-to-end latency of each partition has partially improved, with some partitions recovering while others are still offset. This is marked as suspected dual-domain interleaving. The adjusted local clock readings of each partition are used as the clean clock baseline. The clean clock baseline, the suspected dual-domain interleaving markers, and the dual-suspicion records of the network domain and clock domain are carried to the acquisition centralized controller to perform concurrent command load and receipt distribution. The adjusted local clock readings of each partition are indexed and associated with their corresponding unique identifiers to form a clean clock baseline dataset with timestamps. The clean clock baseline dataset and domain affiliation tags are encapsulated into input data packets for the acquisition central controller's concurrent command load and receipt distribution.

[0022] This embodiment also provides the following: collecting the concurrent command load and response distribution of the centralized controller, specifically: The link quality monitoring parameter set output by the link quality monitoring channel is obtained to form a link quality time series. The link quality monitoring channel refers to the monitoring system embedded in the regular communication frame, which is deployed to establish the partition topology and reference propagation delay. By collecting the signal strength indicator field, signal-to-noise ratio indicator field, retransmission count field, and single-hop delay field in real time, a time series data stream of wireless link transmission quality in each partition is formed. The link quality monitoring parameter set includes the signal strength monitoring value, signal-to-noise ratio monitoring value, retransmission rate monitoring value, and single-hop delay monitoring value of each partition controller. The signal strength monitoring value of each partition controller refers to the current link signal power level reading measured by the wireless receiving module. The signal-to-noise ratio monitoring value is the ratio reading of signal power to background noise power. The retransmission rate monitoring value is the ratio of the number of times the data packet is repeatedly sent due to transmission failure to the total number of transmissions per unit time. The single-hop delay monitoring value is the propagation time of the signal in a single hop between two adjacent network nodes. The latency jitter sequences of each partition are correlated and compared with the time-series records of environmental variables. The latency jitter sequence is a derived analysis sequence representing the amplitude and direction of latency fluctuations, obtained by further extracting the single-hop latency dimension from the link quality time series and processing it through differential operations. If the peak time in the delay jitter sequence coincides with the time when the environmental variable deteriorates, and the delay jitter amplitude increases with the degree of environmental variable deterioration and decreases with the improvement of environmental variable, then it is determined that there is a strong correlation between the delay jitter of this partition and the environmental disturbance, and the link quality sensitivity index of this partition is determined to be of high sensitivity level. If the peak time in the delay jitter sequence does not coincide with the time when the environmental variable deteriorates, and the delay jitter amplitude is independent of the change in the environmental variable, then it is determined that there is no correlation between the delay jitter of this partition and the environmental disturbance, and the link quality sensitivity index of this partition is determined to be low sensitivity level. If both of the above conditions are partially met, it is determined that there is a weak correlation between the latency jitter of the partition and the environmental disturbance, and the link quality sensitivity index of the partition is determined to be of medium sensitivity level. The concurrent load monitoring parameter set output by the concurrent load monitoring channel is obtained to form a concurrent load time series. The concurrent load monitoring parameter set includes the total number of instructions issued per unit time, the current depth sequence of the gateway sending queue, and the distribution sequence of the arrival time of response receipts of each partition. The total number of instructions issued per unit time refers to the data column formed by arranging the total number of instructions sent by the centralized gateway to each partition in a continuous statistical time window in chronological order. The current depth sequence of the gateway sending queue refers to the data column formed by arranging the sampled values ​​of the number of instructions that have not yet been sent in the centralized gateway sending buffer at different times in chronological order. The distribution sequence of the arrival time of response receipts of each partition refers to the time series formed by arranging the time points of the receipts of each partition arriving at the centralized gateway in the order of the linkage cycle number. The latency jitter sequences of each partition are correlated and compared with the concurrent load time series: If the peak time in the latency jitter sequence coincides with the time of concurrent load surge, and the latency jitter amplitude increases with increasing concurrent load and decreases with decreasing concurrent load, then it is determined that there is a strong correlation between the latency jitter and concurrent load in this partition, and the concurrent load sensitivity index of this partition is determined to be high sensitivity level. If the peak time in the latency jitter sequence does not coincide with the time of concurrent load surge, and the latency jitter amplitude is independent of the changes in concurrent load, then it is determined that there is no correlation between the latency jitter and concurrent load in this partition, and the concurrent load sensitivity index of this partition is determined to be low sensitivity level. If both of the above conditions are partially met, then it is determined that there is a weak correlation between the latency jitter and concurrent load in this partition, and the concurrent load sensitivity index of this partition is determined to be medium sensitivity level. Obtain the network topology mapping table for establishing partition topology and baseline propagation delay records, the hop count of each partition, and the current system concurrent load setting value. The hop count of each partition refers to the number of relay nodes traversed by data forwarding between each partition controller and the central gateway in the network topology mapping table for establishing partition topology and baseline propagation delay records plus one. The current system concurrent load setting value refers to the number of commands issued simultaneously, which is manually set and kept constant, and is used to control test variables to eliminate the interference of concurrent load fluctuations on topology distance gradient measurement. Under the condition that the current system concurrent load setting remains constant, probe frames are sent to partitions with different hop counts and end-to-end latency measurements are collected. The measured end-to-end delay values ​​of each partition are grouped according to the number of hops. Topological distance gradient change characteristics are then determined. Grouping the measured end-to-end delay values ​​of each partition according to the number of hops is based on the unique identifier and hop count correspondence recorded in the network topology mapping table. Partitions with the same number of hops are grouped into the same test group, while partitions with different numbers of hops are grouped into different test groups. If the mean of the end-to-end delay measured in the high-hop-count group is greater than the mean of the end-to-end delay measured in the low-hop-count group, and the difference increases monotonically with the number of hops, then it is determined that the delay is systematically amplified with the increase of topological distance, and the gradient change feature is determined to be a significant distance gradient. If the difference between the mean values ​​of the end-to-end delay measured in each hop group is less than the preset distance-independent threshold, then the delay is determined to be independent of the topological distance, and the gradient change feature is determined to be distance-independent. If both of the above conditions are partially met, then the gradient change feature is determined to be weakly distance-dependent. The dispersion of the measured end-to-end latency of each partition within different hop count groups is obtained. Distribution consistency characteristics are determined and sensitive components are extracted. This process yields the dispersion of the measured end-to-end latency of each partition within different hop count groups, i.e., the difference in measured end-to-end latency between partitions within the same hop count group is calculated. If the dispersion of the measured end-to-end delay values ​​of each partition within the same hop count group is less than the preset intra-group consistency threshold, and the difference in the mean of the measured end-to-end delay values ​​between different hop count groups is greater than the preset inter-group difference threshold, then the distribution consistency characteristic is determined to be intra-group consistency and inter-group significant difference. The preset intra-group consistency threshold is the maximum allowable difference for determining whether the measured end-to-end delay values ​​of each partition within the same hop count group are sufficiently close and belong to the same statistical population. The preset inter-group difference threshold is the minimum allowable difference for determining whether there is a significant difference in the mean of the measured end-to-end delay values ​​between different hop count groups. If the dispersion of the measured end-to-end delay values ​​of each partition within the same hop count group is greater than or equal to the preset intra-group consistency threshold, and the difference in the mean of the measured end-to-end delay values ​​between different hop count groups is less than or equal to the preset inter-group difference threshold, then the distribution consistency characteristic is determined to be intra-group discrete and inter-group convergent. If neither of the above two conditions is met, then the distribution consistency characteristic is determined to be weak consistency. The link quality sensitivity index, concurrent load sensitivity index, gradient change characteristics, and distribution consistency characteristics are summarized into a comprehensive feature set of sensitive components; Obtain the sensitive component comprehensive feature set, the clean clock baseline dataset, and the domain attribution label for generating the consistent output of the linked execution results; The sensitive component comprehensive feature set is indexed and associated with the pure clock baseline dataset to form a sensitive component dataset with clock reference. The sensitive component dataset with clock reference and domain affiliation tags are encapsulated into an input data packet for preliminary attribution analysis of partition delay anomalies.

[0023] This embodiment also provides a preliminary attribution analysis for partition latency anomalies, specifically: The system acquires a clean clock baseline dataset, a sensitive component comprehensive feature set, and a current system diagnostic mode identifier. The current system diagnostic mode identifier is a state flag representing the current diagnostic stage of the system, used to control the branching direction of the diagnostic process. Its value includes network domain subdivision mode, clock domain locking mode, and dual-domain interleaving fine screening mode. It is jointly determined by the domain attribution flag and dual-domain interleaving suspicion flag of the generated linkage execution consistency result output. If the generated linkage execution consistency result determines that the causal locking root cause is clock drift accumulation, then the current system diagnostic mode identifier is set to clock domain locking mode. If the generated linkage execution consistency result determines that the causal exclusion is clock domain and confirms that the problem belongs to the network domain, then the current system diagnostic mode identifier is set to network domain subdivision mode. If the generated linkage execution consistency result determination flag is dual-domain interleaving suspicion, then the current system diagnostic mode identifier is set to dual-domain interleaving fine screening mode. If the current system diagnostic mode is identified as network domain segmentation mode, it is determined that the root cause lock-in start condition in the network domain is met, the clean clock baseline dataset is loaded as the current diagnostic clock reference, and the local timing unit of each partition controller is synchronously calibrated with this clock reference. If the current system diagnostic mode identifier is not network domain subdivision mode, it is determined that the start-up conditions are not met, and the communication anomaly type is determined and the corresponding lighting zone linkage control strategy is output. Obtain the link quality sensitivity index level, concurrent load sensitivity index level, link quality sensitivity judgment threshold, and concurrent load sensitivity judgment threshold for each partition. The link quality sensitivity index level refers to the judgment result of high sensitivity level, medium sensitivity level, or low sensitivity level. The concurrent load sensitivity index level refers to the judgment result of high sensitivity level, medium sensitivity level, or low sensitivity level. The link quality sensitivity judgment threshold refers to the level boundary standard for judging whether the link quality sensitivity index exceeds the limit. The concurrent load sensitivity judgment threshold refers to the level boundary standard for judging whether the concurrent load sensitivity index exceeds the limit. For the link quality sensitivity index level, determine the link quality sensitivity index threshold: If the level is high sensitivity or medium sensitivity, the link quality sensitivity index is determined to exceed the preset threshold. If the level is low sensitivity, it is determined that the link quality sensitivity index does not exceed the preset threshold. For the concurrency load sensitivity index level, the concurrency load sensitivity index threshold is determined: If the level is high sensitivity or medium sensitivity, the concurrent load sensitivity index is determined to exceed the preset threshold. If the level is low sensitivity, it is determined that the concurrent load sensitivity index does not exceed the preset threshold; Perform a comprehensive determination of topological distance correlation: Acquire the gradient change characteristics and distribution consistency characteristics of the concurrent command load and receipt distribution of the centralized controller, and establish a network topology mapping table of partition topology and reference propagation delay records; If the gradient change characteristic is that there is a significant distance gradient, and the distribution consistency characteristic is that it is consistent within the group and the difference between the groups is significant, then the determination delay is systematically amplified as the topological distance increases, that is, the delay of the far-end partition is significantly higher than that of the near-end partition. If the gradient change characteristic is distance-independent and the distribution consistency characteristic is discrete within the group and convergent or weakly consistent between groups, then it is determined that the delay offset of each partition is independent of the topological distance, that is, the delay difference between single-hop direct-connected partitions and multi-hop remote partitions is irregular. If both of the above conditions are partially met, then the topological distance correlation feature is determined to be atypical. Root cause determination of communication latency jitter: Obtain the results of the link quality sensitivity index threshold determination, the concurrent load sensitivity index threshold determination, and the comprehensive determination result of topology distance correlation; If the link quality sensitivity index exceeds the preset threshold, and the concurrent load sensitivity index does not exceed the preset threshold, and the topology distance correlation determination result is that the delay offset of each partition is not related to the topology distance, then the communication delay jitter root cause locking condition is met, the cause and effect locking root cause is communication delay jitter, the communication delay jitter determination conclusion is output and recorded as the network domain root cause locking result; If any of the above three conditions is not met, then the communication delay jitter root cause lockout condition is not met. Perform network congestion root cause identification: Obtain the results of the link quality sensitivity index threshold determination, the concurrent load sensitivity index threshold determination, and the comprehensive determination result of topology distance correlation; If the concurrent load sensitivity index exceeds the preset threshold, and the link quality sensitivity index does not exceed the preset threshold, and the topology distance correlation determination result is that the latency is systematically amplified as the topology distance increases, then the network congestion root cause locking condition is met, the causal root cause is locked as network congestion, the network congestion determination conclusion is output and recorded as the network domain root cause locking result. If any of the above three conditions are not met, then the network congestion root cause locking condition is not met. Perform root cause identification and diagnostic output within the network domain: Obtain the results of communication latency jitter root cause lockout, network congestion root cause lockout, link quality sensitivity index threshold, and concurrent load sensitivity index threshold; If the communication delay jitter lockout determination result is satisfied and the network congestion lockout determination result is not satisfied, then output a single communication delay jitter root cause conclusion, execute the determination of the communication anomaly type and output the corresponding lighting zone linkage control strategy. If the communication delay jitter lockout determination result is not met and the network congestion lockout determination result is met, then output a single network congestion root cause conclusion, execute the determination of the communication anomaly type and output the corresponding lighting zone linkage control strategy. If the communication delay jitter lockout determination result is not met and the network congestion lockout determination result is also not met, and the link quality sensitivity index exceeds the preset threshold and the concurrent load sensitivity index exceeds the preset threshold, then it is determined that the dual factors of communication delay jitter and network congestion are intertwined, the dual factor intertwining conclusion is output, the communication anomaly type is determined and the corresponding lighting zone linkage control strategy is output. If none of the above three conditions are met, it is determined that the root cause lock in the network domain is not clear. The initial attribution results are verified by combining the environmental disturbance information with the clean clock baseline dataset carrying the consistent results of the generated linkage execution and the dual suspect records of the network domain and clock domain. The above judgment results are summarized into a network domain root cause lockout decision output dataset.

[0024] This embodiment also provides a consistency verification of the preliminary attribution results by incorporating environmental disturbance information, specifically as follows: The system obtains the adjusted local clock readings of each partition in the clean clock baseline dataset that generates the consistency results of the linkage execution, the system low load judgment threshold, and the current number of concurrent instructions. The system low load judgment threshold refers to the upper limit of the number of concurrent instructions for determining whether the system is currently in a low load running state, and the current number of concurrent instructions refers to the total number of instructions issued by the central gateway to each partition at a certain moment. If the current number of concurrent instructions is less than or equal to the system low load judgment threshold, the system is determined to be in a low load state. Using the clean clock baseline as the time reference, a reference probe frame is sent to each partition, and the measured end-to-end delay value from instruction issuance to execution feedback return is recorded. This measured end-to-end delay value is written into the dual-modal fine screening reference dataset as the end-to-end delay reference value of each partition. The reference probe frame refers to the standard data packet sent by the central gateway to each partition during the dual-modal fine screening reference state establishment phase to measure the end-to-end propagation delay. The measured end-to-end delay value refers to the complete one-way transmission time measurement value from the moment the reference probe frame is issued by the central gateway until the final arrival time of the corresponding partition controller receiving and executing the execution feedback and returning to the central gateway. The dual-modal fine screening reference dataset refers to the data set that records the end-to-end delay reference value measured by each partition under the clean clock baseline condition and low load operation state, and establishes an index association with the unique identifier of the corresponding partition. If the current number of concurrent instructions is greater than the system low load judgment threshold, the system is determined not to be in a low load state. The baseline state establishment operation is then performed after the number of concurrent instructions is reduced to below the system low load judgment threshold. That is, after the system is in a low load state and the clocks of each partition are calibrated to a clean baseline through the generation and linkage execution consistency results, the central gateway sends a baseline probe frame to each partition, collects the end-to-end delay measured value returned by the instruction, and writes it into the dual-modal fine screening baseline dataset as the end-to-end delay baseline value of each partition. The system acquires the end-to-end delay reference value, concurrent load test start amount, concurrent load test end amount, and concurrent load test step increment for each partition in the dual-modal fine screening benchmark dataset. The end-to-end delay reference value for each partition in the dual-modal fine screening benchmark dataset refers to the end-to-end delay reference value of each partition measured under clean clock baseline and low load conditions. The concurrent load test start amount refers to the initial number of concurrent instructions in the stepped concurrent load test. The concurrent load test end amount refers to the maximum number of concurrent instructions allowed in the stepped concurrent load test. The concurrent load test step increment refers to the increase in the number of concurrent instructions between adjacent load test steps. Starting from the initial value of the concurrent load test, the number of partition commands issued simultaneously is increased in a stepwise manner with the concurrent load test increment as the interval, until the concurrent load test termination value is reached. Under the number of concurrent instructions for each step, probe frames are sent to each partition and the measured end-to-end latency values ​​are recorded to form a sequence of measured end-to-end latency values ​​for each step. The average end-to-end delay of each step is compared with the average end-to-end delay of the previous step: If the average end-to-end delay of a certain step increases by more than the average end-to-end delay of the previous step than the preset pulse jump threshold, and this increase continues to expand as the number of concurrent commands continues to increase, then the step is determined to be a pulse jump point, and the pulse component of network congestion is significant. If the average end-to-end delay of all steps does not exceed the preset pulse jump threshold, then no pulse jump point is detected and the pulse component of network congestion is not significant. If the increase of some steps exceeds the preset pulse jump threshold, but the increase of subsequent steps falls back or fluctuates, then the pulse component characteristics are determined to be atypical. The number of concurrent commands that do not have a pulse transition point is obtained as a fixed concurrent load setting value, or the starting value of concurrent load measurement is taken as a fixed concurrent load setting value. The fixed concurrent load setting value refers to the number of concurrent commands that are manually set and remain unchanged throughout the entire observation window during the long-period delay tracking stage. Under the condition that the fixed concurrent load setting remains unchanged, the measured end-to-end delay values ​​of each partition in multiple long-period observation windows are continuously recorded. The average end-to-end delay of each observation window is calculated to form an end-to-end delay mean time series. Specifically, to calculate the average end-to-end delay of each observation window, all the measured end-to-end delay values ​​collected in the observation window are summed to obtain the total end-to-end delay. Then, the total end-to-end delay is divided by the total number of measured end-to-end delay values ​​collected in the observation window. The quotient is the average end-to-end delay of the observation window. Compare the end-to-end delay mean values ​​of adjacent observation windows in the end-to-end delay mean time series: If the average end-to-end delay of subsequent observation windows is consistently greater than the average end-to-end delay of the previous observation window, and this growth trend remains stable throughout all observation windows, then the delay trend line is determined to show a continuous upward trend, and the cumulative component of clock drift is significant. If the end-to-end delay mean of the subsequent observation window fluctuates around a certain fixed value without a monotonically increasing trend, then the delay trend line is considered to be stable and the cumulative component of clock drift is not significant. If some observation windows in the end-to-end mean time series increase and some observation windows decrease, without a stable trend, then the cumulative component characteristics are determined to be atypical. Perform dual-modal component dominance determination and generate an evidence set: If the pulse component is significant and the cumulative component is not significant, then the network congestion pulse component is determined to be the dominant component in the dual-modal interleaving scenario. The number of concurrent commands corresponding to the pulse transition point, the sequence of measured end-to-end delay values ​​for each step, and the pulse component significance determination results are written into the modal component evidence set. The modal component evidence set refers to the data set that records the significance determination results of the network congestion pulse component and the clock drift cumulative component, the specific delay data corresponding to each component, the dominant component attribution identifier, and the non-detection conclusion during the dual-modal interleaving fine screening process. It is used to support the modal component evidence input for the final causal determination of sending unified clock calibration commands to each partition through an independent time synchronization intervention channel. If the pulse component is not significant but the cumulative component is significant, then the clock drift cumulative component is determined to be the dominant component in the dual-modal interleaving scenario, and the end-to-end delay mean time series, the growth trend slope characteristics and the significance determination results of the cumulative component are written into the modal component evidence set. If both the impulse component and the cumulative component are significant, then both modal components are determined to be significant, and the evidence from the impulse component and the evidence from the cumulative component are written together into the modal component evidence set. If the pulse component is not significant and the cumulative component is not significant, it is determined that neither of the two modal components is detected, and the conclusion of non-detection and the original time delay data are written into the modal component evidence set. Obtain modal component evidence sets, clean clock baseline datasets, and dual-suspect records that are not explicitly locked in the root cause locking decision output dataset within the network domain; The modal component evidence set is indexed and associated with the clean clock baseline dataset to form a modal component evidence dataset with baseline correction; The modal component evidence dataset with reference correction and the dual-suspect record are encapsulated into a final causal adjudication input data packet, which serves as modal component evidence for sending unified clock calibration instructions to each partition through an independent time intervention channel for final causal adjudication.

[0025] This embodiment also provides sending a unified clock calibration command to each partition through an independent time synchronization intervention channel, specifically: Acquire modal component evidence set, current system diagnostic mode identifier, current status identifier of time intervention command channel, and clean clock baseline dataset that generates a record of consistent results of linkage execution by combining environmental disturbance information to verify the consistency of preliminary attribution results; Determine the triggering conditions for the second time-synchronization intervention: If the modal component evidence set is invalid, or the current system diagnostic mode is not identified as dual-domain interleaved fine screening mode, or the current status of the time-based intervention command channel is identified as occupied, then it is determined that the triggering conditions for the second time-based intervention are not met, and the system waits until all three conditions are met before determining that the triggering conditions for the second time-based intervention are met. If the modal component evidence set is a valid output and the current system diagnostic mode is identified as dual-domain interleaved fine screening mode and the current status of the time synchronization intervention command channel is identified as idle, then the conditions for triggering the second time synchronization intervention are met, that is, the subsequent operation of sending a unified clock calibration command to each partition through the independent time synchronization intervention channel is executed. Get the current number of concurrent instructions, the system low load threshold, and the standard clock source timestamp; Perform a second time synchronization command issuance condition determination: If the current number of concurrent instructions is less than or equal to the system low load judgment threshold, the system is determined to be in a fixed low load state. A second forced time synchronization instruction is sent to all partition controllers through an independent time synchronization intervention instruction channel. This second forced time synchronization instruction carries the standard clock source timestamp. If the current number of concurrent instructions is greater than the system low load judgment threshold, the system is determined not to be in a fixed low load state, and the sending operation is performed after the number of concurrent instructions is reduced to below the system low load judgment threshold. Obtain the local clock readings before and after the second forced time synchronization command received by each zone controller; Each zone controller, based on the standard clock source timestamp in the second forced time synchronization command, corrects the local clock reading before the second adjustment to the reference time corresponding to the standard clock source timestamp, generates the local clock reading after the second adjustment, and returns a second calibration confirmation receipt to the central controller. The central controller receives secondary calibration confirmation receipts from each zone controller and records the secondary adjustment readings of the local clocks for each zone. The dual-modal fine screening benchmark dataset contains the arrival time of the secondary calibration confirmation receipt of each zone controller after the second time synchronization intervention, the measured end-to-end time delay of each zone, and the end-to-end time delay benchmark value of each zone in the dual-modal fine screening benchmark dataset, which is used to verify the consistency of the preliminary attribution results in combination with environmental disturbance information. The measured end-to-end delay values ​​of each partition are compared with the corresponding end-to-end delay reference values ​​to obtain the delay deviation of each partition. That is, the measured end-to-end delay value of a certain partition is compared with the end-to-end delay reference value in the dual-modal fine screening reference dataset of that partition, which records the consistency verification of the preliminary attribution results combined with environmental disturbance information. If the measured end-to-end delay value is greater than the end-to-end delay reference value, the delay deviation of that partition is the difference between the measured end-to-end delay value and the end-to-end delay reference value. If the measured end-to-end delay value is less than or equal to the end-to-end delay reference value, the delay deviation of that partition is the difference between the end-to-end delay reference value and the end-to-end delay measured value, or it is zero. Obtain the latency deviation of each partition, the latency recovery judgment threshold, and the total number of system partitions; Ultimate arbitration determination of the root cause of accumulated clock drift: For the latency deviation of each partition, if the latency deviation is less than or equal to the latency recovery judgment threshold, then the latency of that partition is determined to have been recovered. If the delay deviation is greater than the delay recovery judgment threshold, then the delay of that partition is determined to have not been recovered. The number of partitions whose latency has been recovered; If the number of partitions whose latency has been recovered is equal to the total number of system partitions, then it is determined that the end-to-end latency of each partition immediately returns to the end-to-end latency baseline value, the out-of-synchronization phenomenon completely disappears, the time accumulation trend line is completely flattened, the causal locking root cause is clock drift accumulation, and the conclusion that clock drift accumulation dominates is output. If the number of partitions whose latency has been recovered is greater than zero and less than the total number of system partitions, it is determined to be a dual-modal interleaving; If the number of partitions whose latency has been recovered is zero, it is determined that the end-to-end latency of each partition has not changed significantly, the nonlinear jump still exists and the time accumulation trend line has not been flattened, the causal lock root cause is network congestion, and the conclusion of network congestion dominance is output. Obtain latency recovery statistics, the number of partitions whose latency has been recovered, and the number of partitions whose latency has not been recovered; Perform bimodal interleaved root cause final arbitration determination and contribution quantification output: If the number of partitions whose latency has been recovered is equal to the total number of system partitions, then it is determined that the clock drift accumulation dominant root cause lock has been completed, and the determination will not be repeated. If the number of partitions whose latency has been recovered is zero, it is determined that the root cause of network congestion has been identified and will not be determined again. If the number of partitions whose latency has been recovered is greater than zero and less than the total number of system partitions, then the latency is determined to be partially improved, with some partitions having recovered latency while others have not. The causal relationship is determined to be bimodal interleaving. The proportion of the number of partitions whose latency has been recovered to the total number of system partitions is quantified as the contribution of the clock drift cumulative component, and the proportion of the number of partitions whose latency has not been recovered to the total number of system partitions is quantified as the contribution of the network congestion pulse component. The dual-mode interleaving determination conclusion, the cumulative contribution of clock drift component, and the contribution of network congestion pulse component are written into the modal component evidence set, and the dual-mode interleaving root cause final arbitration conclusion is output. The system determines the type of communication error and outputs the corresponding lighting zone linkage control strategy.

[0026] Example 4 is an improvement on Example 3. In this example, the communication anomaly type is determined and the corresponding lighting zone linkage control strategy is output, specifically as follows: Obtain the domain affiliation marker, the network domain root cause locking arbitration output dataset, the modal component evidence set, and the root cause final arbitration conclusion; Perform repair strategy matching and differentiated repair: If the root cause is determined to be clock drift accumulation, or if the domain affiliation is identified as clock drift accumulation, then the repair strategy is determined to be the clock domain repair strategy. This triggers forced time synchronization or crystal oscillator temperature compensation calibration. Specifically, based on the clock domain repair strategy, a forced time synchronization command is sent to each partition controller to immediately correct the local clock offset, or temperature compensation calibration is performed on the crystal oscillator hardware to eliminate long-term accumulated deviations caused by temperature drift and restore the consistency of the time base of each partition. The clock domain repair strategy refers to a set of repair measures taken to restore the consistency of the local time base of each partition for a linkage out-of-synchronization fault where the root cause is determined to be clock drift accumulation. These measures include forced time synchronization, which sends a forced calibration command carrying a standard clock source timestamp to all partition controllers through an independent time synchronization intervention command channel to immediately correct the local clock reading; and crystal oscillator temperature compensation calibration, which adjusts the temperature compensation coefficient of the crystal oscillator in the partition controller hardware or replaces it with a high-stability crystal oscillator to reduce the impact of ambient temperature changes on the oscillation frequency and block long-term drift accumulation. If the ultimate arbitration conclusion of the root cause is communication delay jitter, or if the root cause lockout decision output dataset within the network domain contains a single communication delay jitter root cause conclusion, then the repair strategy is determined to be a link quality repair strategy. This triggers link redundancy switching, adaptive transmission power enhancement, or anti-interference coding mechanisms. Specifically, based on the link quality repair strategy, the data transmission path is switched to a backup redundant link, the wireless transmission power is dynamically increased to enhance signal coverage, or anti-interference coding is enabled to reduce the bit error rate, thereby improving communication reliability in harsh environments. The link quality repair strategy refers to a set of repair measures taken to improve the stability and anti-interference capability of wireless communication links for linked out-of-synchronization faults where the root cause is determined to be communication delay jitter. These measures include: link redundancy switching, which switches the data transmission path from the interfered main link to a pre-configured backup redundant link to bypass the faulty section; adaptive transmission power enhancement, which dynamically increases the output power of the wireless transmission module to enhance signal penetration and coverage, compensating for path loss; and anti-interference coding mechanisms, which enable forward error correction coding or spread spectrum modulation technology at the data link layer to improve the recoverability of data packets in noisy environments and reduce the retransmission rate. If the final arbitration conclusion of the root cause is network congestion, or if the root cause lockout dataset within the network domain contains a single network congestion root cause conclusion, then the remediation strategy is determined to be a concurrent load remediation strategy. This triggers batch distribution of instructions, edge cache preloading, or gateway bandwidth expansion. Specifically, based on the concurrent load remediation strategy, all concurrent instructions are split into multiple batches for staggered distribution, common control strategies are pre-configured at edge nodes to reduce real-time transmission volume, or gateway hardware bandwidth is expanded to improve concurrent processing capabilities, thus alleviating the concurrent pressure on large-scale nodes. The concurrent load remediation strategy refers to the coordinated action taken when the root cause is determined to be network congestion. The set of remedial measures taken to address the out-of-synchronization failure, aimed at resolving the congestion in the centralized gateway's sending queue and network bandwidth bottlenecks, includes: batching of instructions, which breaks down the originally planned all-at-once linkage instructions into multiple batches and sends them at preset time intervals to avoid instantaneous overflow of the gateway's sending queue; edge cache preloading, which pre-configures common scenario control strategies in multi-hop relay nodes or edge computing nodes to reduce the transmission frequency and data volume of real-time control instructions; and gateway bandwidth expansion, which upgrades the hardware processing capabilities of the centralized gateway, increases the sending buffer capacity, or improves the outgoing link bandwidth to increase the system's concurrent processing limit. If the root cause final arbitration conclusion is bimodal interleaving, or if the root cause locking arbitration output dataset in the network domain contains bimodal interleaving conclusions, then the repair strategy is determined to be a combined repair strategy, and the contribution of clock drift cumulative component and network congestion pulse component in the modal component evidence set is obtained. If the cumulative contribution of clock drift is greater than the contribution of network congestion pulse, the clock domain repair strategy is executed sequentially before the concurrent load repair strategy. If the cumulative contribution of clock drift is less than or equal to the contribution of network congestion pulse, the concurrent load repair strategy is executed sequentially according to priority before the clock domain repair strategy. If the contributions of the two are equal, then both repair strategies will be executed simultaneously. Execution of repair commands and monitoring of execution status: Obtain the repair strategy type, the corresponding repair parameter set, and the unique identifier for each partition; The repair parameter set is encapsulated into a repair instruction frame and sent to the corresponding partition controller or centralized gateway through a regular communication channel or a time-synchronization intervention instruction channel. The system collects execution confirmation receipts returned by each partition controller, gateway sending queue status feedback, and real-time signal strength monitoring values ​​output by the link quality monitoring channel in real time, forming a repair execution status monitoring dataset. Determining the trigger conditions for initial verification and closed-loop validation of repair effectiveness: Obtain the arrival time of the execution confirmation receipt for each partition in the repair execution status monitoring dataset, the actual brightness feedback value of each partition in the first linkage cycle after repair, and the status switching time of each partition in the first linkage cycle after repair; The actual brightness feedback values ​​of each zone in the first linkage cycle after repair will be compared with the target brightness setting values: If the deviation between the actual brightness feedback value and the target brightness setting value of at least one partition exceeds the brightness tolerance threshold, the initial test of the repair effect is deemed to have failed. If the deviation between the actual brightness feedback value and the target brightness setting value of all partitions does not exceed the brightness tolerance threshold, the initial test of the repair effect is deemed to have passed. The state switching times of each partition in the first linkage cycle after repair are compared with the standard timing reference: if the deviation between the state switching time of at least one partition and the standard timing reference exceeds the timing tolerance threshold, it is determined that the linkage synchronization failure has not been eliminated. If the deviation between the state switching time of all partitions and the standard timing reference does not exceed the timing tolerance threshold, then the linkage synchronization failure is determined to be eliminated. If the initial test of the repair effect fails or the linkage synchronization failure is not eliminated, it is determined that the closed-loop verification triggering condition is not met, and the third time synchronization intervention experiment and end-to-end time delay closed-loop verification are directly executed. If the repair effect passes the initial test and the linkage loss has been eliminated, it is determined that the closed-loop verification trigger condition is met, and the third time synchronization intervention experiment and end-to-end time delay closed-loop verification are executed. The third time-intervention experiment and end-to-end time delay closed-loop verification were conducted: Acquire the current status identifier of the time intervention command channel, the standard clock source timestamp, and the end-to-end time delay reference value of each partition in the dual-modal fine screening benchmark dataset; If the current status of the time synchronization intervention command channel is idle, it is determined that the triggering condition for the third time synchronization intervention is met. The third forced time synchronization command is sent to all partition controllers through an independent time synchronization intervention command channel. The third forced time synchronization command carries the standard clock source timestamp. If the current status of the time synchronization intervention command channel is marked as occupied, it is determined that the conditions for triggering the third time synchronization intervention are not met, and the transmission operation will be performed after the channel becomes idle. Each zone controller corrects its local clock based on the standard clock source timestamp in the third forced time synchronization command and returns three calibration confirmation receipts to the central controller. After receiving three calibration confirmation receipts, the central controller sends verification probe frames to each partition and collects the end-to-end delay measurement values. It then compares the end-to-end delay measurement values ​​of each partition with the corresponding end-to-end delay reference values ​​to obtain the closed-loop verification delay deviation of each partition. Reset the closed-loop verification result judgment and diagnosis process: Obtain the closed-loop verification delay deviation, delay recovery judgment threshold, and total number of system partitions for each partition; For the closed-loop verification delay deviation of each partition, if the closed-loop verification delay deviation is less than or equal to the delay recovery judgment threshold, then the closed-loop verification delay of that partition is determined to have been recovered. If the closed-loop verification delay deviation is greater than the delay recovery judgment threshold, it is determined that the closed-loop verification delay of that partition has not been recovered; count the number of partitions whose closed-loop verification delay has been recovered. If the number of partitions whose closed-loop verification latency has been recovered is equal to the total number of system partitions, then it is determined that the end-to-end latency of each partition has returned to the end-to-end latency baseline value, the linkage synchronization loss has been eliminated, the closed-loop verification is passed, and the repair process is terminated. If the number of partitions whose closed-loop verification delay has been recovered is less than the total number of system partitions, the deviation is still deemed to exceed the limit and the closed-loop verification fails. The current system diagnostic mode is then reset to the initial screening start mode. The collected end-to-end delay measurement values ​​are used as a new apparent feature dataset. Periodic measurements of outbound and return delays are re-executed, and the bidirectional delay deviation sequence is calculated to start a new round of progressive diagnosis, forming a closed-loop verification system anchored by the time-intervention experiment.

[0027] In this embodiment, the timing intervention experiment is upgraded from an auxiliary verification to a core mechanism for causal determination, enabling accurate adjudication of root causes in the network and clock domains. Through a three-layer progressive diagnostic architecture, the misjudgments of communication latency jitter, network congestion, and clock drift accumulation are decoupled and locked layer by layer. Through link quality-concurrent load dual-dimensional isolation tracing and topological distance gradient decay analysis, the root causes within the network domain are finely distinguished. Through differentiated repair strategies and timing intervention closed-loop verification, the repair effect is confirmed instantly and the diagnostic process is adaptively reset. Ultimately, this improves the fault diagnosis accuracy, repair efficiency, and system operation stability of the landscape lighting zone linkage control.

Claims

1. A method for zoned linkage control of landscape lighting, characterized in that: include: Under low load conditions, the bidirectional communication delay between each partition and the central controller is collected to establish the partition topology and the reference propagation delay. Periodically measure the outbound and return delays, and calculate the bidirectional delay deviation sequence; Based on the differences between the brightness feedback of each partition and the target brightness, as well as the linkage timing deviation, a consistent linkage execution result is generated. The load and response distribution of concurrent commands from the centralized controller are collected to obtain load status parameters; Based on bidirectional latency deviation, load status, and topology hop count, a preliminary attribution analysis is performed on partition latency anomalies. The consistency of the preliminary attribution results was verified by combining environmental disturbance information to distinguish between environmental impacts and link factors; When a clock synchronization offset exceeding the threshold is detected, a unified clock calibration command is sent to each partition through an independent time synchronization intervention channel. Based on the time delay changes before and after calibration, the communication anomaly type is determined and the corresponding lighting zone linkage control strategy is output.

2. The landscape lighting zone linkage control method according to claim 1, characterized in that: Establish the partition topology and baseline propagation delay, specifically as follows: Obtain the basic attribute dataset of the landscape zoning of the target landscape region; The landscape area is divided into several independent control zones based on functional attribute labels, and a unique identifier is assigned to each zone. Establish an adjacency table for adjacent partitions based on physical boundary coordinates; Establish a cross-zone linkage priority index based on the level of illumination demand; This data is aggregated to form a global spatial topology network. Acquire the spatial coordinates of the planned deployment locations in each zone, the sensing radius of each type of sensor, and the obstacle distribution data within the zone; For any spatial point within the partition, perform a completeness verification of the perception coverage; Obtain the set of communication network hardware capability parameters; Construct a wireless communication network consisting of a centralized gateway, multi-hop relay nodes, and a partition controller; By embedding a transmission timestamp field, a reception timestamp field, a signal strength indicator field, a signal-to-noise ratio indicator field, and a retransmission count field into a regular communication frame, a link quality monitoring indicator structure is formed. Obtain the network link transmission characteristic parameter set from each partition controller to the central gateway; If there is a direct physical connection path between a certain partition controller and the central gateway, then the partition is determined to be a directly connected partition, and its hop count is recorded as one. If a partition controller and the central gateway need to forward data via a relay node, then the partition is determined to be a relay partition, and its hop count is recorded as the number of relay nodes plus one. Establish a network topology mapping table to record the partition network topology attribute records for each partition; Under low system load conditions, send reference probe frames to each partition and record round-trip latency; Half of the measured round-trip time is written into the network topology mapping table as the historical baseline propagation time for that partition; Obtain the configuration parameter set for the concurrent load monitoring channel; A concurrent load monitoring channel is established on the centralized controller side to record the concurrent load real-time monitoring dataset per unit time, forming a concurrent load monitoring dataset. A separate channel for real-time intervention commands is reserved in the system.

3. The landscape lighting zone linkage control method according to claim 1, characterized in that: Periodically measure the outbound and return delays, and calculate the bidirectional delay deviation sequence, specifically: Obtain the linkage out-of-synchronization detection parameter set of the lighting execution terminals in each zone; For any linkage cycle, trigger linkage out-of-synchronization judgment and domain isolation initial screening; Acquire the following records: the time when the gateway sends probe frames to each partition controller, the time when each partition controller receives probe frames, the time when each partition controller sends back response frames, and the final arrival time of the response frames received by the gateway. Based on the transmission and reception time records, the outbound propagation delay of the signal from the gateway to the partition controller is determined; Based on the return time record and the final arrival time record, the return propagation delay of the signal from the partition controller to the gateway is determined; The outbound and return propagation delays are associated with the corresponding partitions and linkage cycle numbers to form a single-cycle bidirectional delay record; Obtain single-cycle bidirectional delay records for multiple consecutive linkage cycles to obtain a sequence of differences between outbound and return propagation delays for each partition. Analyze the distribution characteristics of this difference sequence; Acquire the environmental disturbance monitoring parameter set of each partition during the transmission of the probe frame, and form a time series record of environmental variables; The outbound and return propagation delay sequences of each partition are correlated and compared with the environmental variable time series records, respectively. Based on the combined characteristics of bidirectional time delay asymmetry and the results of the time delay environment correlation determination, the domain isolation is initially screened and the direction is determined.

4. The landscape lighting zone linkage control method according to claim 1, characterized in that: Generate consistent results for coordinated execution, specifically as follows: Acquire the feature acquisition completion identifier, the current status identifier of the time intervention command channel, and the standard clock source timestamp; Acquire the local clock readings before and after adjustment of each zone controller after receiving the forced time synchronization command, and perform zone local clock calibration and collect calibration confirmation receipts. Acquire the arrival time of the calibration confirmation receipt of each partition controller after the time intervention is completed, the measured end-to-end delay of each partition, and the historical reference propagation delay for establishing partition topology and reference propagation delay records; The measured end-to-end delay values ​​of each partition are compared with the corresponding historical benchmark propagation delay to obtain the delay deviation of each partition. Obtain the latency deviation of each partition, the latency recovery judgment threshold, and the total number of system partitions; For the latency deviation of each partition, compare the latency deviation with the latency recovery judgment threshold; The number of partitions whose latency has been recovered; If the number of partitions whose latency has been recovered is equal to the total number of system partitions, then it is determined that the end-to-end latency of each partition immediately returns to the historical reference propagation latency, the out-of-synchronization phenomenon completely disappears, and the root cause of the causal lock is the accumulation of clock drift. If the number of partitions whose latency has been recovered is zero, it is determined that there is no significant change in the end-to-end latency of each partition, the out-of-synchronization phenomenon still exists, the clock domain is ruled out as the cause, and the problem is confirmed to belong to the network domain. If the number of partitions whose latency has been recovered is greater than zero and less than the total number of system partitions, then it is determined that the end-to-end latency of each partition has partially improved, with some partitions recovering while others are still offset, and is marked as suspected dual-domain interleaving. The adjusted local clock readings of each partition are indexed and associated with their corresponding unique identifiers to form a clean clock baseline dataset with timestamps. The clean clock baseline dataset and domain affiliation tags are encapsulated into input data packets for the acquisition central controller's concurrent command load and receipt distribution.

5. The landscape lighting zone linkage control method according to claim 1, characterized in that: The distribution of concurrent command load and response data from the centralized controller is collected, specifically as follows: Obtain the link quality monitoring parameter set output by the link quality monitoring channel to form a link quality time series; The latency jitter sequences of each partition are correlated and compared with the time series records of environmental variables; Obtain the set of concurrent load monitoring parameters output by the concurrent load monitoring channel to form a concurrent load time series; The latency jitter sequence of each partition is correlated and compared with the concurrent load time series; Obtain the network topology mapping table for establishing partition topology and baseline propagation delay records, the hop count of each partition, and the current system concurrent load setting; Under the condition that the current system concurrent load setting remains constant, probe frames are sent to partitions with different hop counts and end-to-end latency measurements are collected. The measured end-to-end delay values ​​of each partition are grouped according to the number of hops, and the topological distance gradient change characteristics are determined. The dispersion of the measured end-to-end latency values ​​of each partition within different hop count groups is obtained, and the distribution consistency characteristics are determined and sensitive components are extracted. The link quality sensitivity index, concurrent load sensitivity index, gradient change characteristics, and distribution consistency characteristics are summarized into a comprehensive feature set of sensitive components; Obtain the sensitive component comprehensive feature set, the clean clock baseline dataset, and the domain attribution label for generating the consistent output of the linked execution results; The sensitive component comprehensive feature set is indexed and associated with the pure clock baseline dataset to form a sensitive component dataset with clock reference. The sensitive component dataset with clock reference and domain affiliation tags are encapsulated into an input data packet for preliminary attribution analysis of partition delay anomalies.

6. The landscape lighting zone linkage control method according to claim 1, characterized in that: A preliminary attribution analysis was conducted on the partition latency anomalies, specifically as follows: Obtain the clean clock baseline dataset, the sensitive component comprehensive feature set, and the current system diagnostic mode identifier; If the current system diagnostic mode is identified as network domain segmentation mode, it is determined that the root cause lock-in start condition in the network domain is met, the clean clock baseline dataset is loaded as the current diagnostic clock reference, and the local timing unit of each partition controller is synchronously calibrated with this clock reference. If the current system diagnostic mode identifier is not network domain subdivision mode, it is determined that the start-up conditions are not met, and the communication anomaly type is determined and the corresponding lighting zone linkage control strategy is output. Obtain the link quality sensitivity index level, concurrent load sensitivity index level, link quality sensitivity judgment threshold, and concurrent load sensitivity judgment threshold for each partition; For the link quality sensitivity index level, determine the link quality sensitivity index threshold; For the concurrency load sensitivity index level, a concurrency load sensitivity index threshold determination is performed; Perform a comprehensive determination of topological distance correlation; Perform root cause determination of communication latency jitter; Perform network congestion root cause identification; Perform root cause identification and diagnostic output within the network domain.

7. The landscape lighting zone linkage control method according to claim 1, characterized in that: The consistency of the preliminary attribution results was verified by incorporating environmental disturbance information, specifically as follows: Obtain the adjusted local clock readings of each partition in the clean clock baseline dataset that generates the consistency results of the linked execution, the system low load judgment threshold, and the current number of concurrent instructions; If the current number of concurrent instructions is less than or equal to the system low load judgment threshold, the system is judged to be in a low load state. Using the clean clock baseline as the time reference, a reference probe frame is sent to each partition and the measured end-to-end delay value from instruction issuance to execution feedback is recorded. The measured end-to-end delay value is written into the dual-modal fine screening reference dataset as the end-to-end delay reference value of each partition. If the current number of concurrent instructions is greater than the system low load judgment threshold, the system is determined not to be in a low load state, and the baseline state establishment operation is performed after the number of concurrent instructions is reduced to below the system low load judgment threshold. Obtain the end-to-end time delay baseline value, concurrent load test start value, concurrent load test end value, and concurrent load test step increment for each partition in the dual-modal fine screening benchmark dataset; Starting from the initial value of the concurrent load test, the number of partition commands issued simultaneously is increased in a stepwise manner with the concurrent load test increment as the interval, until the concurrent load test termination value is reached. Under the number of concurrent instructions for each step, probe frames are sent to each partition and the measured end-to-end latency values ​​are recorded to form a sequence of measured end-to-end latency values ​​for each step. The average end-to-end delay of each step is compared with the average end-to-end delay of the previous step. The number of concurrent instructions that do not exhibit a pulse transition point is used as the fixed concurrent load setting value; Under the condition that the fixed concurrent load setting remains unchanged, the measured end-to-end delay values ​​of each partition in multiple long-period observation windows are continuously recorded, the average end-to-end delay of each observation window is calculated, and the end-to-end delay average time series is formed. Compare the end-to-end delay mean values ​​of adjacent observation windows in the end-to-end delay mean time series; Perform dual-modal component dominance determination and generate an evidence set; Obtain modal component evidence sets, clean clock baseline datasets, and dual-suspect records that are not explicitly locked in the root cause locking decision output dataset within the network domain; The modal component evidence set is indexed and associated with the clean clock baseline dataset to form a modal component evidence dataset with baseline correction; The modal component evidence dataset with benchmark correction and the dual-suspect record are encapsulated into the ultimate causal adjudication input data package.

8. The landscape lighting zone linkage control method according to claim 1, characterized in that: A unified clock calibration command is sent to each zone through an independent time synchronization intervention channel, specifically as follows: Acquire modal component evidence set, current system diagnostic mode identifier, current status identifier of time intervention command channel, and clean clock baseline dataset that generates a record of consistent results of linkage execution by combining environmental disturbance information to verify the consistency of preliminary attribution results; Perform a second time-based intervention trigger condition determination; Get the current number of concurrent instructions, the system low load threshold, and the standard clock source timestamp; Perform a second time synchronization command issuance condition determination; Obtain the local clock readings before and after the second forced time synchronization command received by each zone controller; Each zone controller, based on the standard clock source timestamp in the second forced time synchronization command, corrects the local clock reading before the second adjustment to the reference time corresponding to the standard clock source timestamp, generates the local clock reading after the second adjustment, and returns a second calibration confirmation receipt to the central controller. The central controller receives secondary calibration confirmation receipts from each zone controller and records the secondary adjustment readings of the local clocks for each zone. The dual-modal fine screening benchmark dataset contains the arrival time of the secondary calibration confirmation receipt of each zone controller after the second time synchronization intervention, the measured end-to-end time delay of each zone, and the end-to-end time delay benchmark value of each zone in the dual-modal fine screening benchmark dataset, which is used to verify the consistency of the preliminary attribution results in combination with environmental disturbance information. The measured end-to-end delay values ​​of each partition are compared with the corresponding end-to-end delay reference values ​​to obtain the delay deviation of each partition. Obtain the latency deviation of each partition, the latency recovery judgment threshold, and the total number of system partitions; The ultimate arbitration determination is made based on the cumulative root cause of clock drift. Obtain latency recovery statistics, the number of partitions whose latency has been recovered, and the number of partitions whose latency has not been recovered; Perform dual-modal interleaved root cause final arbitration determination and contribution quantification output; The system determines the type of communication error and outputs the corresponding lighting zone linkage control strategy.

9. The landscape lighting zone linkage control method according to claim 1, characterized in that: Determine the type of communication error and output the corresponding lighting zone linkage control strategy, specifically: Obtain the domain affiliation marker, the network domain root cause locking arbitration output dataset, the modal component evidence set, and the root cause final arbitration conclusion; Perform repair strategy matching and differentiated repair; Execution of repair command issuance and execution status monitoring; Determine the triggering conditions for preliminary verification of repair effectiveness and closed-loop verification. The third time-intervention experiment and end-to-end time delay closed-loop verification were carried out. Reset the closed-loop verification result judgment and diagnosis process.

Images