Information transmission method and device for aviation obstacle light

Abstract

The application provides an information transmission method and device for aviation obstruction lights, relates to the field of information transmission, and solves the technical problems of high failure rate of terminals and delayed reporting of sudden failure events caused by the inability to dynamically adjust according to the real-time state of the terminal. The method comprises the following steps: based on the number of aviation obstruction lights in each sub-region in the coverage area of the aviation obstruction lights and the failure rate of the aviation obstruction lights in each sub-region, assigning a number to the target terminal corresponding to each aviation obstruction light. Set the communication period, divide the communication period into a downlink instruction transmission stage, an uplink data return stage and an event reporting stage. In the downlink instruction transmission stage, set a downlink exclusive communication time slot for each target terminal, and in the uplink data return stage, set an uplink exclusive communication time slot for each target terminal. The time slot length of the exclusive communication time slot is dynamically adjusted by the number data of the target terminal. The application is used in the information transmission process of aviation obstruction lights.

Description

Technical Field

[0001] This application relates to the field of information transmission, and in particular to an information transmission method and apparatus for aviation obstruction lights. Background Technology

[0002] Aviation obstruction lights are critical equipment for ensuring aircraft flight safety. Their technological development is closely related to the progress of the aviation industry, urbanization, and the upgrading of safety standards. Currently, the mainstream communication management of aviation obstruction lights still adopts a static time slot allocation mechanism: the system presets a fixed length of communication time slot for each terminal, and the central controller polls all terminals in a fixed order to complete data interaction. This mechanism can meet basic needs in early scenarios with a small number of terminals and stable operating status. However, in complex scenarios, the real-time status of terminals in different areas varies significantly. For example, some terminals experience increased failure rates due to high altitude and highly corrosive environments, while some terminals need to transmit emergency alarm data (such as light source failure or voltage abnormality). Fixed time slots cannot be allocated resources preferentially. At the same time, when aviation malfunction lights experience sudden failure events, they must wait for a complete polling cycle before being received by the controller, resulting in response delays. Low-priority terminals (such as stable low-level equipment) occupy fixed time slots, causing resource idleness, while high-priority terminals (such as top-level critical equipment) face data congestion due to insufficient time slots, forming a "resource mismatch" problem. Summary of the Invention

[0003] This application provides an information transmission method and apparatus for aviation obstruction lights, which solves the technical problem that the prior art cannot dynamically adjust resources according to the real-time status of the terminal (such as failure rate, data type priority), resulting in data delay reporting of terminals with high failure rates, and the need to wait for a full cycle to respond to sudden failure events.

[0004] To achieve the above objectives, this application adopts the following technical solution:

[0005] Firstly, a method for transmitting information using aviation obstruction lights includes: assigning a number to a target terminal corresponding to each aviation obstruction light based on the number of aviation obstruction lights in each sub-area within the coverage area of ​​the aviation obstruction light and the failure rate of the aviation obstruction lights in each sub-area. The target terminal corresponding to each aviation obstruction light is a terminal installed on the aviation obstruction light for collecting information from it.

[0006] The communication cycle is set and divided into a downlink command transmission stage, an uplink data return stage, and an event reporting stage. The downlink command transmission stage is used for the central controller to issue commands to the target terminal. The uplink data return stage is used for the target terminal to report the status of the aviation obstruction lights to the central controller. The event reporting stage is used for the target terminal to report sudden events of the aviation obstruction lights to the central controller.

[0007] In the downlink command transmission phase, a dedicated downlink communication time slot is set for each target terminal. In the uplink data return phase, a dedicated uplink communication time slot is set for each target terminal. The length of the dedicated communication time slot is dynamically adjusted based on the target terminal's identification number.

[0008] Send a first indication message to the target terminal. The first indication message is used to indicate the target terminal's dedicated communication time slot and communication cycle.

[0009] Based on the above technical solution, this application provides an information transmission method for aviation obstruction lights. By setting a dynamic terminal numbering structure based on the number and failure rate of aviation obstruction lights in a sub-region, and setting dedicated communication time slots according to different dynamic terminal numbering structures during the downlink command phase and uplink return phase, the terminal failure rate simultaneously affects the numbering (indirect control) and the time slot formula (direct control), achieving dual protection for high-risk equipment. This ensures that communication resources are precisely matched with equipment risks and real-time requirements, thereby reducing the transmission latency of critical data (such as fault warnings) from high-failure-risk terminals and improving reliability under limited bandwidth.

[0010] In conjunction with the first aspect mentioned above, in one possible implementation, based on the number of aviation obstruction lights in each sub-region of the aviation obstruction light coverage area and the failure rate of the aviation obstruction lights in each sub-region, a number is assigned to the target terminal corresponding to each aviation obstruction light. This includes: dividing the aviation obstruction light coverage area into multiple sub-regions according to physical location, and obtaining the number of aviation obstruction lights in each sub-region. The average failure rate of terminals in each sub-region is statistically analyzed from historical data, and the region weight is calculated. Sub-regions are arranged in descending order of region weight, with terminals in high-weight regions assigned numbers first. Within the same sub-region, terminals are assigned numbers in ascending order of failure rate. When the number of terminals decreases, the numbers of the reduced terminals are reserved as free numbers for allocation to subsequently added terminals. When the number of terminals increases, free numbers are assigned to new terminals; if no free numbers are available, new numbers are assigned to new terminals. The region weights and terminal failure rates are periodically recalculated to update the numbering sequence.

[0011] In conjunction with the first aspect mentioned above, in one possible implementation, the length of the dedicated communication time slot is dynamically adjusted based on the target terminal's identification data. This includes: calculating a composite time slot coefficient based on the target terminal's identification number and the failure rate of aviation obstruction lights within each sub-region, combined with the priority weight of the target terminal's data type and the channel quality factor, to obtain the base length of the dedicated time slot. An LSTM model is used to predict the data volume of the target terminal in the next communication cycle. If the predicted data volume for the next communication cycle exceeds a burst threshold, a compensation time slot is generated. The sum of the base length of the dedicated time slot and the compensation time slot is calculated to determine the final time slot length. When the centralized controller receives an event alarm, preemptive scheduling of event data is activated.

[0012] In conjunction with the first aspect mentioned above, in one possible implementation, based on the target terminal number and the failure rate of the aviation obstruction light within each sub-region, combined with the priority weight of the target terminal's data type and the channel quality factor, a composite time slot coefficient is calculated to obtain the dedicated time slot base length. This includes: dynamically generating the priority weight of the data type according to the data type reported by the target terminal; periodically sending test data packets via the RS485 bus, calculating the instantaneous bit error rate, and converting it into a channel quality factor; and based on the target terminal number i and the aviation obstruction light failure rate F... i Priority weight P of the target terminal data type i Channel quality factor Q i and number offset δ i ,pass Calculate the composite coefficient, where N is the total number of terminals, and the number offset is determined by... The calculations show that α, β, and γ are configurable weights, and ln(1+N) is the numbering compensation term. The basic time slot length is generated by combining the minimum guaranteed time slot and the numbering increment coefficient, which are obtained from the parameter configuration file of the centralized controller.

[0013] In conjunction with the first aspect mentioned above, one possible implementation involves using an LSTM model to predict the data volume of the target terminal in the next communication cycle. If the predicted data volume for the next communication cycle exceeds a burst threshold, a compensation time slot is generated. This time slot includes: inputting the historical data volume sequence of the terminal for M consecutive cycles and the fault events of the aviation information fault lights within the same cycle. A dual-channel LSTM model is then constructed, and the dual-channel LSTM model fuses the predicted values ​​from both channels through an attention mechanism. The burst threshold is dynamically set based on the data type reported by the target terminal, where the formula for setting the burst threshold is... , of which Sudden threshold, The largest historical data volume, ρ is the overfitting prevention attenuation coefficient, and D base The base threshold is used, and μ is the failure rate sensitivity coefficient. When the predicted data volume exceeds the burst threshold, [further action is taken]. Generate compensation time slots, where T unit This refers to the single-byte transmission latency.

[0014] In conjunction with the first aspect mentioned above, in one possible implementation, when the centralized controller receives an event alarm, activating preemptive scheduling of event data includes: parsing the urgency level identifier in the event alarm; Level 1 identifier indicates hardware failure; Level 2 identifier indicates parameter out-of-bounds error; Level 3 identifier indicates abnormal status; and setting trigger conditions for Level 1 identifier to trigger a hardware interrupt signal, and Level 2 and Level 3 identifiers to trigger a software interrupt. Idle dedicated time slots when terminals have no data transmission needs during the current communication cycle and remaining time slots after terminal transmission are completed are divided into micro-time slots, and the number of micro-time slots is allocated according to the event urgency level identifier. If a single terminal has insufficient micro-time slots, the time slots of adjacent low-priority terminals are merged to form an event transmission block. The centralized controller broadcasts a time slot borrowing instruction, and the borrowed terminal suspends its own service to forward event data. The terminal corresponding to the fault event sends a complete data packet through the aggregated time slot. After the fault event transmission is completed, the interrupted terminal resumes transmission from the breakpoint, and the centralized controller adds compensation time slots for the borrowed terminal.

[0015] In conjunction with the first aspect mentioned above, in one possible implementation, the downlink command transmission phase includes: the central controller broadcasting a control command containing the target terminal number via the bus. Each terminal controller listens to the bus signal in real time, extracts the number information from the command, and verifies the consistency between the number information in the command and the target terminal's own number. If the target terminal's own number does not match the command number, the command data is actively discarded. If the target terminal's own number matches the command number, and verification is performed through a dedicated communication time slot, the command is executed.

[0016] In conjunction with the first aspect mentioned above, in one possible implementation, the uplink data backhaul phase includes: dividing the uplink data backhaul phase into a data backhaul period and a micro-synchronization period. During the data backhaul period, each terminal sends status data to the central controller via the bus within its dedicated communication time slot. Upon entering the micro-synchronization period, the central controller verifies the integrity of the status data and initiates a precise retransmission request for missing terminals. The central controller broadcasts a synchronization calibration signal, and each terminal compensates for clock drift based on the calibration signal. A periodic synchronization confirmation flag is generated, triggering the start of the next communication cycle.

[0017] In conjunction with the first aspect mentioned above, in one possible implementation, the event reporting phase includes: setting tiered response rules based on event alarm levels: For Level 1 fault events, a hardware interrupt signal is triggered, allowing preemption of any terminal's dedicated time slot. For Level 2 fault events, a software interrupt signal is triggered, allowing preemption only of time slots dedicated to terminals in the same area or with lower priority. For Level 3 fault events, a status flag is triggered, transmitting only in idle time slots or at the end of a cycle. When multiple event alarms occur concurrently, preemption priority is allocated in descending order of event level; events of the same level are arbitrated in ascending order of terminal failure rate.

[0018] Secondly, an information transmission device for aviation obstruction lights is provided, comprising: a communication unit and a processing unit; the communication unit is used to acquire the number of aviation obstruction lights in each sub-area of ​​the aviation obstruction light coverage area, and the failure rate of the aviation obstruction lights in each sub-area.

[0019] The processing unit assigns a number to the target terminal corresponding to each aviation obstruction light based on the number of aviation obstruction lights in each sub-area of ​​the aviation obstruction light coverage area and the failure rate of the aviation obstruction lights in each sub-area. The target terminal corresponding to each aviation obstruction light is a terminal installed on the aviation obstruction light to collect information from the aviation obstruction light. A communication cycle is set, divided into a downlink command transmission stage, an uplink data return stage, and an event reporting stage. The downlink command transmission stage is used for the central controller to issue commands to the target terminal; the uplink data return stage is used for the target terminal to report the status of the aviation obstruction light to the central controller; and the event reporting stage is used for the target terminal to report sudden events of the aviation obstruction light to the central controller. A dedicated downlink communication time slot is set for each target terminal during the downlink command transmission stage, and a dedicated uplink communication time slot is set for each target terminal during the uplink data return stage. The length of the dedicated communication time slot is dynamically adjusted based on the target terminal's number data. A first indication message is sent to the target terminal, indicating the dedicated communication time slot and communication cycle of the target terminal.

[0020] Thirdly, this application provides an information transmission device for aviation obstruction lights, comprising: a processor and a storage medium; the storage medium includes instructions, and the processor is configured to execute the instructions to implement the method described in the first aspect and any possible implementation thereof. This information transmission device for aviation obstruction lights can be an electronic device or a chip within an electronic device.

[0021] Fourthly, this application provides a computer-readable storage medium storing instructions that, when executed on the information transmission device for aviation obstruction lights, cause the information transmission device for aviation obstruction lights to perform the methods described in the first aspect and any possible implementation thereof.

[0022] Fifthly, this application provides a computer program product containing instructions that, when the computer program product is run on the information transmission device for aviation obstruction lights, causes the information transmission device for aviation obstruction lights to perform the methods described in the first aspect and any possible implementation thereof.

[0023] This application provides an information transmission method and apparatus for aviation obstruction lights. It can set a dynamic terminal numbering structure based on the number and failure rate of aviation obstruction lights in a sub-region, and set dedicated communication time slots according to different dynamic terminal numbering structures during the downlink command phase and uplink return phase. This allows the terminal failure rate to simultaneously affect the numbering (indirect control) and the time slot formula (direct control), achieving dual protection for high-risk equipment. It ensures that communication resources are precisely matched with equipment risks and real-time requirements, thereby reducing the transmission latency of critical data (such as fault warnings) from high-failure-risk terminals and improving reliability under limited bandwidth.

[0024] It should be understood that the descriptions of technical features, technical solutions, beneficial effects, or similar language in this application do not imply that all features and advantages can be achieved in any single embodiment. Rather, it is understood that the description of a feature or beneficial effect means that a specific technical feature, technical solution, or beneficial effect is included in at least one embodiment. Therefore, the descriptions of technical features, technical solutions, or beneficial effects in this specification do not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions, and beneficial effects described in this embodiment can be combined in any suitable manner. Those skilled in the art will understand that embodiments can be implemented without one or more specific technical features, technical solutions, or beneficial effects of a particular embodiment. In other embodiments, additional technical features and beneficial effects may be identified in specific embodiments that do not embody all embodiments. Attached Figure Description

[0025] Figure 1 A system architecture diagram for an information transmission method for aviation obstruction lights is provided in this application embodiment;

[0026] Figure 2 A flowchart illustrating an information transmission method for aviation obstruction lights provided in an embodiment of this application;

[0027] Figure 3 A flowchart illustrating another information transmission method for aviation obstruction lights provided in an embodiment of this application;

[0028] Figure 4 A flowchart illustrating another information transmission method for aviation obstruction lights provided in an embodiment of this application;

[0029] Figure 5 This is a schematic diagram of the structure of an information transmission device for aviation obstruction lights provided in an embodiment of this application. Detailed Implementation

[0030] In the description of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. The "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. The terms "first," "second," etc., do not limit the quantity or order of execution, and "first," "second," etc., do not necessarily imply differences.

[0031] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0032] To address the significant differences in real-time terminal status across different areas in complex scenarios, existing technologies face challenges. For instance, some terminals experience increased failure rates due to high altitudes or corrosive environments, while others require transmitting urgent alarm data (such as light source failure or voltage anomalies). Fixed time slots cannot prioritize resource allocation, and aviation fault lights require a full polling cycle before being received by the controller during sudden malfunctions, leading to response delays. Low-priority terminals (such as stable lower-level devices) occupy fixed time slots, resulting in resource idleness, while high-priority terminals (such as top-level critical devices) face data congestion due to insufficient time slots, creating a "resource mismatch" problem. Furthermore, traditional master-slave polling mechanisms require the master station to send requests one by one and wait for responses, lacking dedicated time slot guarantees, leading to excessively long waiting times for subsequent devices and unpredictable uplink latency. Random access mechanisms based on CSMA / CA or ALOHA are prone to data collisions and retransmissions in shared bus scenarios such as RS485, reducing transmission reliability. Furthermore, existing technologies rely on hybrid event-driven or heartbeat packet reporting strategies, making it difficult to achieve strong synchronous updates of the entire system status. Some device statuses (such as "silent faults") may be missed due to lack of change, and the centralized controller cannot obtain a global instantaneous snapshot, affecting the technical problems of monitoring accuracy and diagnostic efficiency. This application provides an information transmission method for aviation obstruction lights. This method obtains the dynamic numbering structure of terminals by using the number and failure rate of aviation obstruction lights in sub-regions, and sets exclusive communication time slots according to different dynamic numbering structures of terminals during the downlink command stage and uplink backhaul stage. This allows the terminal failure rate to simultaneously affect the numbering (indirect control) and the time slot formula (direct control), achieving dual protection for high-risk devices. It ensures that communication resources are precisely matched with device risks and real-time requirements, thereby reducing the transmission latency of key data (such as fault warnings) of high-failure-risk terminals and improving reliability under limited bandwidth.

[0033] like Figure 1 As shown in the figure, an information transmission method for aviation obstruction lights provided in this application includes:

[0034] Step 101: Based on the number of aviation obstruction lights in each sub-area within the aviation obstruction light coverage area, and the failure rate of the aviation obstruction lights in each sub-area, assign a number to the target terminal corresponding to each aviation obstruction light. The target terminal corresponding to the aviation obstruction light is a terminal installed on the aviation obstruction light for collecting information about the aviation obstruction light.

[0035] The aviation obstruction light coverage area refers to the physical space where aviation obstruction lights need to be installed (such as high-rise buildings, towers, mountainous areas, etc.), which is divided into several sub-areas. The target terminal is a data acquisition and transmission device installed on the aviation obstruction light, used to collect real-time status information of the light (such as faults and brightness) and transmit this information to the central controller. The failure rate refers to the probability of an aviation obstruction light malfunctioning within a sub-area, calculated based on historical data (number of failures / total runtime). The number is a unique logical identifier assigned to the target terminal, used for communication addressing and resource scheduling priority ranking.

[0036] In some implementations, the coverage area of ​​aviation obstruction lights is divided, and the number of aviation obstruction lights and their failure rate within the divided sub-areas are obtained. Based on the number of aviation obstruction lights and their failure rate within the sub-areas, dynamic numbering and allocation rules are formulated. Each target terminal is assigned a number according to the actual situation of each sub-area, and the numbering can directly affect the allocation of dedicated time slots during the communication phase.

[0037] Step 102: Set the communication cycle, which is divided into a downlink command transmission stage, an uplink data return stage, and an event reporting stage. The downlink command transmission stage is used for the central controller to issue commands to the target terminal. The uplink data return stage is used for the target terminal to report the status of the aviation obstruction lights to the central controller. The event reporting stage is used for the target terminal to report sudden events of the aviation obstruction lights to the central controller.

[0038] The communication cycle refers to a fixed-time loop unit for communication between the centralized controller and the target terminal, ensuring controllable system timing. The downlink command transmission phase refers to the period within the cycle during which the centralized controller broadcasts commands (such as controlling light switching or parameter adjustments) to the target terminal via the bus. The uplink data feedback phase refers to the period within a dedicated time slot during which the target terminal reports the routine status of the aviation obstruction lights to the centralized controller (such as brightness and current values). The event reporting phase refers to the period during which the target terminal actively reports unexpected events (such as malfunctions or external damage), independent of the routine status feedback.

[0039] It should be noted that the three phases are executed sequentially within the cycle and do not overlap, avoiding bus conflicts (the terminal does not send data until the downlink phase is completed). Simultaneously, during the uplink phase, a clock calibration signal resolves clock drift issues between terminals, ensuring the accuracy of subsequent cycle startups. The event reporting phase is configured with a reserved period so that when a sudden event occurs, there is no need to wait for the uplink phase. The current phase can be interrupted directly upon the occurrence of the sudden event, activating the event reporting phase to directly transmit the event data. After the event data transmission is complete, the system returns to the interrupted point to continue the phase before the interruption, ensuring the real-time nature of high-priority alarms.

[0040] The downlink command transmission phase includes: the central controller broadcasts a control command containing the target terminal's number via the bus. Each terminal controller listens to the bus signal in real time and extracts the number information from the command. It then matches and verifies the consistency between the number information in the command and the target terminal's own number. If the target terminal's own number does not match the command number, the command data is discarded. If the target terminal's own number matches the command number, and verification is performed through a dedicated communication time slot, the command is executed.

[0041] The uplink data backhaul phase is divided into a data backhaul period and a micro-synchronization period. During the data backhaul period, each terminal sends status data to the central controller via the bus within its dedicated communication time slot. Upon entering the micro-synchronization period, the central controller verifies the integrity of the status data and initiates precise retransmission requests for missing terminals. The central controller broadcasts a synchronization calibration signal, and each terminal compensates for clock drift based on the calibration signal. A periodic synchronization confirmation flag is generated, triggering the start of the next communication cycle.

[0042] The event reporting phase includes: setting tiered response rules based on event alarm levels: For Level 1 fault events, a hardware interrupt signal is triggered, allowing preemption of any terminal's dedicated time slot. For Level 2 fault events, a software interrupt signal is triggered, allowing preemption only of time slots dedicated to terminals in the same area or with lower priority. For Level 3 fault events, a status flag is triggered, and transmission is only allowed in idle time slots or at the end of a cycle. When multiple event alarms occur concurrently, preemption priority is allocated in descending order of event level; for events of the same level, arbitration is conducted in ascending order of terminal failure rate.

[0043] Step 103: During the downlink command transmission phase, set up a dedicated downlink communication time slot for each target terminal. During the uplink data return phase, set up a dedicated uplink communication time slot for each target terminal. The length of the dedicated communication time slot is dynamically adjusted by the target terminal's identification number.

[0044] In this context, a downlink dedicated communication time slot refers to a fixed time window allocated to each target terminal during the downlink command transmission phase, used to receive commands (such as lighting control commands) issued by the central controller. An uplink dedicated communication time slot refers to a fixed time window allocated to each target terminal during the uplink data return phase, used to report status data (such as voltage and brightness) to the central controller. The time slot length refers to the duration of the dedicated communication time slot, determining the data transmission capacity.

[0045] In some implementations, based on the terminal number and the failure rate of the aviation obstruction light, the appropriate time slot length for different numbers is calculated autonomously, so that terminals with high failure rates trigger larger basic time slots to ensure risk protection. When the amount of data suddenly increases (LSTM prediction exceeds the limit), additional compensation time slots can be added (to deal with emergencies), thereby adapting to the needs of different scenarios.

[0046] Send a first indication message to the target terminal. The first indication message is used to indicate the target terminal's dedicated communication time slot and communication cycle.

[0047] Based on the above technical solution, a dynamic terminal numbering structure is obtained by analyzing the number and failure rate of aviation obstruction lights in sub-regions. Simultaneously, the communication cycle is forcibly divided into three stages: downlink command, uplink transmission, and event reporting. These stages are executed sequentially and without overlap, thus achieving physical isolation, avoiding bus contention, and ensuring deterministic transmission of commands and data. The independent event stage ensures that unexpected events can break through conventional timing constraints, achieving millisecond-level response. Specifically, in the downlink command and uplink transmission stages, a dedicated communication time slot is set for each target terminal according to its different dynamic terminal numbering structure. This allows the terminal failure rate to simultaneously affect both the numbering (indirect control) and the time slot formula (direct control), achieving dual protection for high-risk equipment. This ensures precise matching of communication resources with equipment risk and real-time requirements, thereby reducing the transmission latency of critical data (such as fault warnings) from high-failure-risk terminals and improving reliability within limited bandwidth.

[0048] In one possible implementation of this application embodiment, assigning a number to the target terminal corresponding to each aviation obstruction light based on the number of aviation obstruction lights in each sub-area of ​​the aviation obstruction light coverage area and the failure rate of the aviation obstruction lights in each sub-area can be achieved through the following steps S201 to S205, which are described in detail below:

[0049] Step 201: Divide the coverage area of ​​the aviation obstruction lights into multiple sub-regions according to their physical location, and obtain the number of aviation obstruction lights in each sub-region.

[0050] In some implementations, the entire aviation obstruction light coverage area is divided into several continuous sub-regions based on geographical boundaries (such as building outlines and terrain contour lines) or functional zoning (such as airport runway areas and wind farm areas). For example, mountainous areas are divided into sub-regions every 100 meters of altitude. Urban building clusters are divided by individual buildings or building groups. The registered aviation obstruction light device identifiers (such as device IDs) within each sub-region can be queried through the device registry or GIS (Geographic Information System) database of the centralized controller. The statistical results are then stored in structured data in the format: Sub-region ID - Number of aviation obstruction lights. An update mechanism is set up to automatically scan the online status of devices periodically (e.g., monthly) and dynamically update the number of valid devices within each sub-region. When devices are added or removed, real-time data synchronization to the centralized controller is triggered.

[0051] It should be noted that sub-regions need to meet the requirements of physical location continuity and management convenience, avoid splitting the same device cluster across regions, and if the number of devices in a sub-region is 0 (e.g., due to temporary removal), it is marked as an empty region and does not participate in the weight calculation.

[0052] Step 202: Calculate the average failure rate of terminals in each sub-region of historical data and calculate the region weight.

[0053] Historical data refers to the long-term storage of operational records of terminals (i.e., aviation obstruction light data acquisition equipment) within a sub-region by the centralized controller, including fault events and operating duration. The average failure rate is the ratio of the total number of failures occurring in all terminals within a sub-region during the statistical period to the total operating time (formula: Failure Rate = Total Operating Hours / Number of Failures × 100%). Regional weight is a priority coefficient calculated based on the number of devices and the average failure rate in the sub-region, used to determine the order of numbering (a higher value indicates a higher priority for that region).

[0054] In some implementations, the fault history (such as communication interruption and sensor failure records) of each sub-region terminal is extracted from the central controller database. The single-terminal failure rate is calculated using a formula, and then the arithmetic mean of all terminals within the sub-region is calculated. This allows the data to be analyzed using parameters: the number of devices in the sub-region N, and the average failure rate F. The formula calculates the regional weight W, where α and β are preset coefficients, with α usually > β, highlighting the dominance of the number of devices.

[0055] Step 203: Arrange sub-regions in descending order of regional weight. Terminals in high-weight regions are assigned numbers first. Within the same sub-region, terminals are assigned numbers in ascending order of failure rate.

[0056] The descending order of regional weights sorts sub-regions from highest to lowest calculated weight values ​​(sub-regions with higher weight values ​​are ranked higher). Prioritizing high-weight regions means that in the numbering allocation sequence, terminal devices within sub-regions with higher weight values ​​are processed first. Ascending order of terminal numbers based on failure rate means that within the same sub-region, terminals with lower failure rates are assigned numbers first (ascending failure rate order means sorting by failure rate values ​​from smallest to largest).

[0057] In some implementations, the weight values ​​W of all sub-regions are read and sorted in descending order. For each sub-region, the failure rate of all terminals within it is extracted, and the terminal sequence is arranged in ascending order. This allows for the processing of the sub-region sorting results sequentially, followed by the assignment of consecutive numbers within the current sub-region in ascending order of terminal failure rate (with priority given to terminals with the lowest failure rate).

[0058] For example, first obtain the sub-region weights [7.2, 3.0, 4.8]. Then, generate a sorted list [7.2, 4.8, 3.0] based on the sub-region weights in descending order. Assign the sorted sub-regions [sub-region 1, sub-region 2, sub-region 3] according to their order of arrangement. If sub-region 1 contains 3 terminals with failure rates [0.12%, 0.08%, 0.05%], sort them in ascending order and output the terminal sequence [terminal C, terminal B, terminal A]. At this point, the terminals in sub-region 1 are sorted by failure rate in ascending order as [C, B, A], and assigned numbers 001, 002, and 003 respectively. The terminals in sub-region 2 [D, E] have failure rates in ascending order of [0.03%, 0.10%], and are assigned numbers 004 and 005.

[0059] Step 204: When the number of terminals decreases, the number of the reduced terminals is reserved as a free number for allocation to newly added terminals.

[0060] When the number of terminals increases, an idle number is assigned to the newly added terminal. If no idle number is available, a new number is assigned to the newly added terminal.

[0061] The reduction in the number of terminals refers to the decrease in the number of data acquisition terminals corresponding to aviation obstruction lights in a sub-region due to equipment removal, scrapping, or relocation. Idle numbers refer to the unassigned numbers released by the reduced number of terminals, which are stored in the idle number pool of the central controller and marked as available. The increase in the number of terminals refers to the inclusion of newly installed aviation obstruction light terminals into the management system. New numbers refer to new numbers generated by the central controller according to an incrementing rule (e.g., the original maximum number + 1) when the idle number pool is exhausted.

[0062] In some implementations, the centralized controller detects that a terminal has not responded for three consecutive communication cycles, determines it to be offline, and moves the terminal's original ID to the idle ID pool (e.g., if the original ID 005 is released, 005 is added to the idle pool). The idle ID pool is recorded in the format: [ID, Release Time]. When a terminal is added, the idle ID pool is checked: if an available ID exists, the ID with the earliest release time is selected and assigned to the new terminal; if the idle pool is empty, a new ID is generated: the currently assigned maximum ID N is obtained. max New number = N max +1.

[0063] It should be noted that both idle and newly added numbers are guaranteed to be globally unique to avoid conflicts. The idle number pool has no upper limit, but unused numbers that have expired (such as those idle for more than 30 days) can be automatically cleaned up. Newly added numbers are strictly incremental and are not affected by sub-regions or terminal types.

[0064] Step 205: Periodically recalculate the regional weights and terminals according to the failure rate, and update the numbering sequence.

[0065] Periodic recalculation involves triggering system-level updates at fixed time intervals (e.g., weekly). The updated number sequence is generated by re-establishing the terminal number allocation order based on the latest weight and failure rate data.

[0066] In some implementations, the centralized controller has a built-in timer that automatically initiates an update process at fixed intervals (e.g., monthly). During this update, the number of devices N and the terminal failure rate F in all sub-regions are re-collected (using the same method as the initial calculation), and then calculated according to the formula. Update the weight value of each sub-region, and rearrange the sequence of terminals in each sub-region in ascending order of the latest failure rate. Then, arrange the sub-regions in descending order according to the new weights, and finally generate a global allocation sequence in ascending order of terminal failure rate in each sub-region.

[0067] Based on the above technical solution, sub-regions are divided according to physical location to establish a geographic zoning model. Then, regional weights are calculated based on the number of devices and average failure rate to quantify regional criticality. Finally, sub-regions are arranged in descending order of weight to form a global priority sequence. This allows for the automatic allocation of higher communication priority in densely populated areas or high-failure areas (such as mountaintop wind turbine clusters), reducing data latency in critical areas and avoiding resource waste caused by traditional average allocation. Simultaneously, terminals within the same sub-region are assigned numbers in ascending order of failure rate, prioritizing low-failure devices. Periodically recalculating the failure rate and ranking, and updating the risk status in real time, allows low-failure-rate devices to obtain stable communication resources (such as dedicated time slots), delaying the spread of potential failures. The periodic update mechanism addresses equipment aging and environmental changes (such as failure rate fluctuations caused by salt spray corrosion). Finally, reducing the number of terminals released to the idle pool and establishing a number recycling mechanism, new terminals are prioritized for allocation of idle numbers, achieving closed-loop reuse of numbering resources. When the idle pool is exhausted, new numbers are generated, elastically expanding the resource pool. This increases the numbering reuse rate, avoids resource waste, and allows new devices to be integrated into the system immediately, supporting dynamic network expansion.

[0068] In one possible implementation of this application embodiment, the time slot length of the dedicated communication time slot can be dynamically adjusted by the target terminal's number data, which can be achieved through the following steps S301 to S304, as detailed below:

[0069] Step 301: Based on the target terminal number and the failure rate of the aviation obstruction light in each sub-region, combined with the priority weight of the target terminal data type and the channel quality factor, calculate the composite time slot coefficient to obtain the basic length of the dedicated time slot.

[0070] Based on the data type reported by the target terminal, the priority weight of the data type is dynamically generated.

[0071] Test data packets are periodically sent via RS485 bus to calculate the instantaneous bit error rate and convert it into a channel quality factor.

[0072] Based on the target terminal number i and the failure rate F of the aviation obstruction light i Priority weight P of the target terminal data type i Channel quality factor Q i and number offset δ i ,pass Calculate the composite coefficient, where N is the total number of terminals, and the number offset is determined by... The calculations show that α, β, and γ are configurable weights, and ln(1+N) is the numbered compensation term.

[0073] The basic time slot length is generated by combining the minimum guaranteed time slot and the numbering increment coefficient. The minimum guaranteed time slot and the numbering increment coefficient are obtained from the parameter configuration file of the centralized controller.

[0074] Among them, the data type priority weight P i It is a dynamically generated weight value based on the data type (such as status data, alarm data) reported by the terminal, used to quantify the importance of data (e.g., fault alarms have higher priority than status monitoring). Channel Quality Factor Q i It involves periodically sending test data packets via an RS485 bus to calculate the instantaneous bit error rate and convert it into a communication reliability index (the lower the bit error rate, the higher the Q). i (The higher the value). Composite time slot coefficient K i It is a dynamic coefficient calculated based on the integrated terminal number, failure rate, data type weight, and channel quality factor (formula: This is used to adjust the length of a dedicated time slot. The basic length of the dedicated time slot is determined by the composite coefficient K. i The initial time slot value is generated by combining the system's preset minimum guarantee time slot and numbering increment coefficient.

[0075] In some implementations, the centralized controller parses the type of data reported by the terminals (such as status data, parameter out-of-bounds alarms, and hardware fault events) and dynamically assigns weights according to preset rules. This allows inputting the terminal number i and the failure rate F. i (Originated from historical database), data type weight P i (Dynamically generated), Channel Quality Factor Q i (Converted by test packet bit error rate: Q) i =1 - bit error rate), number offset δ i =N i -1 (the influence of the quantization number position) is directly substituted into the formula to calculate the composite time slot coefficient K. i Then, read the minimum guaranteed time slot (e.g., 100ms) and the numbering increment coefficient (e.g., per unit K) from the central controller's configuration file. i By adding 10ms, the basic time slot can be calculated as: basic time slot = minimum guaranteed time slot + K. i×Incremental coefficient for numbering, used to calculate the base length.

[0076] Step 302: Use the LSTM model to predict the data volume of the target terminal in the next communication cycle. If the predicted data volume of the next communication cycle exceeds the burst threshold, generate a compensation time slot.

[0077] In this context, LSTM stands for Long Short-Term Memory, a recurrent neural network used to process time-series data. It captures long-term dependencies through gating mechanisms (input gate, forget gate, output gate). The predicted data volume refers to the total amount of data the LSTM model predicts the target terminal needs to transmit in the next communication cycle. The burst threshold is a dynamically set critical value for the data volume; exceeding this value triggers the generation of compensation time slots. Compensation time slots are additional communication time windows allocated to handle data bursts.

[0078] In some implementations, a dual-channel LSTM model is constructed by inputting a sequence of historical data from the terminal for M consecutive cycles (e.g., M=10) into channel 1, and inputting the types of fault events of the aviation obstruction lights within the same cycle (e.g., Level 1 hardware failure, Level 2 parameter out-of-bounds). The data is then independently input into the LSTM layer via two channels, and the output is weighted and fused using an attention mechanism to generate predicted values. The threshold is then adjusted based on the terminal data type. If the predicted value generated by the dual-channel LSTM model exceeds the burst threshold, a compensation time slot is generated.

[0079] The system inputs a sequence of historical data from the terminal for M consecutive periods and fault events of the aircraft fault lights within the same period to construct a dual-channel LSTM model. The dual-channel LSTM model then fuses the predicted values ​​from both channels through an attention mechanism.

[0080] The burst threshold is dynamically set based on the data type reported by the target terminal, where the formula for setting the burst threshold is as follows: , of which Sudden threshold, The largest historical data volume, ρ is the overfitting prevention attenuation coefficient, and D base The base threshold is μ, which is the failure rate sensitivity coefficient.

[0081] When the predicted data volume exceeds the burst threshold, through Generate compensation time slots, where T unit This refers to the single-byte transmission latency.

[0082] Step 303: Calculate the sum of the base length of the dedicated time slot and the compensation time slot to determine the final time slot length.

[0083] In some implementations, compensation time slots are generated only when the predicted data volume exceeds the threshold to avoid low-risk terminals occupying additional resources. Therefore, the compensation time slot is an incremental addition to the base length (e.g., base length 100ms + compensation 20ms), rather than overwriting the original value. Thus, the final time slot length needs to be calculated before the start of the communication cycle to ensure that the time slot indication information is sent out in a timely manner.

[0084] Step 304: When the centralized controller receives an event alarm, it activates the preemptive scheduling of event data.

[0085] Among them, event alarm refers to the notification of sudden aviation obstruction light events reported by the target terminal, which includes an emergency level indicator (such as hardware failure, parameter out-of-bounds, or abnormal status), triggering the central controller to initiate a scheduling response. Preemptive scheduling refers to a mechanism that prioritizes event data for communication resources, achieving real-time transmission by interrupting low-priority services and borrowing time slots.

[0086] Based on the above technical solution, and using the input historical data sequence and fault event types, an attention mechanism is employed to output predicted values. Combined with an adaptive burst threshold and an exponential decay compensation formula, a closed-loop control system is formed, encompassing prediction, threshold comparison, and compensation generation. When the burst data volume exceeds the threshold, compensation slots are precisely matched to demand, reducing errors and avoiding the periodic waiting delays of traditional polling. This allows for collaboration with high-failure-rate terminals, which obtain basic resource guarantees through numbering and coefficient formulas, thereby improving slot utilization. Furthermore, upon receiving an event alarm, preemptive scheduling of event data is activated, further enhancing system stability under burst events.

[0087] In one possible implementation of this application embodiment, when the centralized controller receives an event alarm, activating preemptive scheduling of event data can be achieved through the following steps S401 to S404, which are described in detail below:

[0088] Step 401: Analyze the emergency level identifiers in the event alarms. Level 1 indicates a hardware fault, Level 2 indicates a parameter out of bounds, and Level 3 indicates a status abnormality. Set the trigger conditions for Level 1 to trigger a hardware interrupt signal and for Level 2 and Level 3 to trigger software interrupts.

[0089] Level 1 indicates a hardware failure, signifying damage or malfunction of the physical components of the aviation obstruction light (such as sensors or power modules). Level 2 indicates parameter exceeding limits, meaning that critical operating parameters of the equipment (such as voltage, current, or brightness values) exceed preset safety ranges. Level 3 indicates an abnormal state, indicating that the equipment is in an unexpected operating state (such as communication interruption or functional degradation), but not to the severity of hardware damage or parameter exceeding limits. A hardware interrupt signal is a direct hardware-level signal triggered by a Level 1 event, used to immediately interrupt the current system operation, prioritize fault handling, and ensure rapid response. Software interrupt triggering conditions are set for Level 2 and Level 3 events, with conditions (such as event type matching or priority verification) used to activate the software interrupt mechanism, processing the event through the centralized controller's program.

[0090] In some implementations, when a target terminal (such as a data acquisition device for aviation obstruction lights) reports an emergency, the central controller first parses the emergency level identifier field in the event alarm. This identifier is embedded in the alarm data packet and has a fixed encoding format (e.g., Level 1 is binary "01", Level 2 is "10", and Level 3 is "11"). The controller identifies the specific level through a decoding algorithm (such as bit parsing). If the parsing result is a Level 1 identifier (hardware fault), the controller directly activates a hardware interrupt signal. Activating the hardware interrupt signal includes sending an interrupt command to the system bus, forcibly suspending all low-priority tasks, and starting the hardware diagnostic module (such as a fault self-test circuit) to ensure a response within milliseconds. Simultaneously, for Level 2 or Level 3 identifiers, the controller configures software interrupt trigger conditions. These trigger conditions include verifying whether the identifier type (Level 2 is parameter out of bounds or Level 3 is status abnormality) matches preset conditions. Combined with the event emergency level, a software interrupt is triggered only when the conditions are met (e.g., parameter out of bounds threshold is exceeded), starting an interrupt service routine (such as parameter adjustment or status recovery), and processing the event data through a bus scheduling mechanism. Simultaneously, both parsing and triggering are performed during the event reporting phase, ensuring that event processing is separated from the regular communication cycle and avoiding resource conflicts.

[0091] Step 402: Divide the idle dedicated time slots when the terminal has no data transmission needs during the current communication cycle and the remaining time slots after the terminal has completed transmission into micro time slots, and allocate the number of micro time slots according to the event urgency level identifier.

[0092] Event alarms refer to sudden information packets reported by a target terminal (such as the data acquisition equipment of an aviation obstruction light) to the central controller after detecting an abnormal event. These packets include the event type and urgency level. Micro-timeslots are smaller time units (e.g., 1ms) created by cutting idle or remaining dedicated time slots, used for efficient allocation of event transmission resources. Idle dedicated time slots refer to unused dedicated time slots during a communication cycle when the terminal has no data transmission needs (e.g., the unallocated portion during the downstream instruction transmission phase). Remaining time slots refer to unused time segments remaining after the terminal completes data transmission within its dedicated time slot (e.g., the portion of the upstream service dedicated time slot that ends early).

[0093] In some implementations, during the event reporting phase, the central controller scans the current communication cycle: identifying terminal-specific time slots with no data transmission needs (such as idle downlink time slots) and remaining dedicated time slots after transmission is complete (such as the early termination portion of uplink service time slots). These time slots are then divided into micro-time slot units (e.g., dividing one dedicated time slot into five 0.2ms micro-time slots). The division is based on a preset time granularity (e.g., a minimum micro-time slot length of 0.1ms), and the number of micro-time slots is allocated according to the event urgency level: for example, Level 1 events (highest priority) are allocated the most micro-time slots (e.g., 5), allowing preemption of resources. Level 2 events (medium priority) are allocated a medium number (e.g., 3). Level 3 events (lowest priority) are allocated the fewest micro-time slots (e.g., 1), and this process is only executed when there are sufficient micro-time slots.

[0094] Step 403: If a single terminal's micro-time slots are insufficient, merge the time slots of adjacent low-priority terminals to form an event transmission block. The centralized controller broadcasts a time slot borrowing instruction, and the borrowed terminal suspends its own service to forward event data. The terminal corresponding to the fault event sends the complete data packet through the aggregated time slot.

[0095] Insufficient microtimeslots for a single terminal refer to the situation where the number of microtimeslots allocated to a single faulty event terminal (e.g., only 2) is insufficient to transmit a complete event data packet (requiring 5 microtimeslots). Adjacent low-priority terminals are target terminal devices that are physically adjacent in the communication cycle timing (e.g., adjacent numbers) and have a lower current service priority (e.g., Level 3 events or regular status feedback). An event transmission block is a continuous time unit formed by merging multiple microtimeslots (e.g., 5 0.2ms microtimeslots merged into a 1ms block) used to transmit a complete event data packet (fixed length 128 bytes). A timeslot borrowing instruction is a special instruction broadcast by the central controller (format: target terminal ID + borrowing duration), forcing the borrowed terminal to suspend its current service and relinquish bus control. Suspending its own service to forward event data means the borrowed terminal suspends its original planned transmission task (e.g., status feedback), switches to transparent forwarding mode, and directly transmits the faulty event data packet to the bus. An aggregated timeslot is a continuous transmission window formed by splicing the microtimeslots of the borrowed terminal with the original microtimeslots, ensuring that the faulty terminal sends a complete data packet in one go.

[0096] In some implementations, when the number of micro-slots allocated to a faulty terminal (e.g., terminal A, experiencing a Level 1 hardware failure) is less than its data packet requirement (requiring 5 micro-slots), the centralized controller identifies the gap (gap = 2 micro-slots) using a slot counter. The controller then scans the communication cycle sequence to locate the terminal with the lowest physical proximity (e.g., adjacent by ID ±1) and lowest priority (e.g., terminal B performing a Level 3 task, terminal C performing a regular status return). The controller forcibly requisitions the dedicated slots of terminals B and C (1 micro-slot each), merging them with the faulty terminal's original 3 micro-slots into a continuous event transmission block (total length 1ms). The transmission block length must meet the requirements for complete data packet transmission. At this time, the controller broadcasts a borrowing instruction via the bus. Upon receiving this instruction, the borrowing terminals (B and C) immediately suspend their current service (e.g., terminating status return data encapsulation) and switch to transparent forwarding mode, preparing to receive data from the faulty terminal. This allows the faulty terminal (A) to send a complete event data packet (128 bytes) within the aggregated slot (1ms continuous window). The borrowed terminals (B and C) monitor the bus in real time and forward data packets to the central controller as is, ensuring no data loss.

[0097] Step 404: After the fault event transmission is completed, the interrupted terminal continues transmission from the breakpoint, and the central controller adds a compensation time slot for the borrowed terminal.

[0098] In this context, an interrupted terminal refers to a target terminal whose service is forcibly suspended due to event transmission (such as a terminal whose time slot is used to forward event data). The breakpoint refers to the precise location where service transmission is interrupted, recorded by the central controller. A compensation time slot refers to a dedicated time slot resource added by the central controller for the borrowed terminal in subsequent communication cycles to compensate for interruption losses.

[0099] In some implementations, when the borrowed terminal (e.g., terminal B) receives a time slot borrowing instruction, it immediately suspends its current service (e.g., status feedback) and records the breakpoint information (format: data packet sequence number + byte offset) in its local cache. Simultaneously, the central controller synchronously stores this breakpoint (associated with the terminal ID and communication cycle number) in the global interrupt log. At this point, after receiving the complete event data packet, the central controller verifies the data integrity. If the verification passes, it broadcasts a completion confirmation signal, triggering the terminal recovery process. Upon receiving the completion confirmation signal, the borrowed terminal (terminal B) reads the breakpoint from its cache and continues transmitting the remaining data from the breakpoint within its dedicated time slot in the next communication cycle. If the original service data packet spans multiple cycles, it is split for transmission. Simultaneously, the central controller calculates the interruption loss and the compensation time slot length, where: loss = interruption duration × bus rate. Compensation time slot length = loss / bus rate + basic compensation. This means that in the next cycle allocation, a compensation time slot is added to the dedicated time slot of the borrowed terminal (terminal B), and the compensation time slot is used only for the terminal's service transmission and cannot be preempted by other events.

[0100] Based on the above technical solution, the event urgency level classification and interrupt triggering mechanism are implemented through the parsing module (embedded with event data packet processing logic) and interrupt control unit of the centralized controller. This ensures the response to Level 1 events, prevents the spread of equipment damage, and simultaneously ensures that Level 2 and Level 3 events are triggered by software interrupt conditions, reducing CPU load, preventing low-priority events from preempting high-urgency tasks, effectively improving the accuracy of event processing priority, and reducing the average latency of high-priority events. Simultaneously, the time slot management engine implements a dynamic micro-time slot segmentation and hierarchical allocation mechanism, enabling efficient reuse of idle resources, reducing bandwidth waste during communication cycles, and effectively ensuring sufficient resources for critical events (such as hardware failures) by allocating resources according to priority (Level 1 has the highest priority). Under limited resource conditions, it optimizes the fairness of time slot allocation and reduces the average latency of event transmission. Furthermore, the time slot borrowing and aggregation transmission emergency mechanism is implemented through the scheduling module to solve resource shortage problems (such as micro-time slot gaps in Level 1 events), ensuring complete transmission of event data packets (without packet loss). Borrowing time slots from adjacent low-priority terminals (avoiding interference from high-priority terminals) ensures system stability and reduces the risk of data conflicts. Finally, the recovery management module implements breakpoint resume and compensation recovery mechanisms to ensure that interrupted terminal services are not lost (accurate resume from the breakpoint), improve recovery efficiency, and at the same time, the compensation mechanism (such as adding time slots) makes up for resource loss, prevents service backlog, and ensures system throughput balance.

[0101] The foregoing mainly describes the solutions of the embodiments of this application from the perspective of device implementation. It is understood that each device, for example, an information transmission device for aviation obstruction lights, includes at least one of the hardware structures and software modules corresponding to the execution of each function in order to achieve the above-mentioned functions. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software-driven hardware manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0102] This application embodiment can divide the information transmission device for aviation obstruction lights into functional units according to the above method example. For example, each function can be divided into a separate functional unit, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional unit. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0103] When using integrated units, Figure 5 A possible structural schematic diagram of the information transmission device for aviation obstruction lights (referred to as an information transmission device 50 for aviation obstruction lights) involved in the above embodiments is shown. The information transmission device 50 for aviation obstruction lights includes a processing unit 501 and a communication unit 502, and may also include a storage unit 503. Figure 5 The structural diagram shown can be used to illustrate the structure of the information transmission device for aviation obstruction lights involved in the above embodiments.

[0104] when Figure 5 The schematic diagram shown illustrates the structure of the information transmission device for aviation obstruction lights involved in the above embodiments. The processing unit 501 is used to control and manage the operation of the information transmission device for aviation obstruction lights, the communication unit 502 is used for the information transmission device for aviation obstruction lights to communicate with other devices, and the storage unit 503 is used to store the program code and data of the information transmission device for aviation obstruction lights.

[0105] For example, the communication unit 502 is used to obtain the number of aviation obstruction lights in each sub-area of ​​the aviation obstruction light coverage area, as well as the failure rate of the aviation obstruction lights in each sub-area.

[0106] Processing unit 501 is used to assign numbers to target terminals corresponding to each aviation obstruction light based on the number of aviation obstruction lights in each sub-area of ​​the aviation obstruction light coverage area and the failure rate of aviation obstruction lights in each sub-area. The target terminal corresponding to the aviation obstruction light is a terminal installed on the aviation obstruction light for collecting information about the aviation obstruction light.

[0107] The communication cycle is set and divided into a downlink command transmission stage, an uplink data return stage, and an event reporting stage. The downlink command transmission stage is used for the central controller to issue commands to the target terminal. The uplink data return stage is used for the target terminal to report the status of the aviation obstruction lights to the central controller. The event reporting stage is used for the target terminal to report sudden events of the aviation obstruction lights to the central controller.

[0108] In the downlink command transmission phase, a dedicated downlink communication time slot is set for each target terminal, and in the uplink data return phase, a dedicated uplink communication time slot is set for each target terminal. The time slot length of the dedicated communication time slot is dynamically adjusted by the numbering data of the target terminal.

[0109] Send a first indication message to the target terminal, the first indication message being used to indicate the target terminal's dedicated communication time slot and the communication period.

[0110] The processing unit 501 can be a processor or a controller, and the communication unit 502 can be a communication interface, transceiver, transceiver circuit, transceiver device, etc. The term "communication interface" is a general term and may include one or more interfaces. The storage unit 503 can be a memory. When the information transmission device 50 for aviation obstruction lights is a chip, the processing unit 501 can be a processor or a controller, and the communication unit 502 can be an input interface and / or an output interface, pins, or circuits, etc. The storage unit 503 can be a storage unit within the chip (e.g., a register, cache, etc.) or a storage unit located outside the chip (e.g., read-only memory (ROM), random access memory (RAM, etc.)).

[0111] The communication unit can also be called a transceiver unit. The antenna and control circuit with transceiver functions in the information transmission device 50 for aviation obstruction lights can be considered as the communication unit 502 of the information transmission device 50 for aviation obstruction lights, and the processor with processing functions can be considered as the processing unit 501 of the information transmission device 50 for aviation obstruction lights. Optionally, the device in the communication unit 502 that implements the receiving function can be considered as the communication unit, which is used to execute the receiving steps in the embodiments of this application. The communication unit can be a receiver, a receiver circuit, etc. The device in the communication unit 502 that implements the transmitting function can be considered as the transmitting unit, which is used to execute the transmitting steps in the embodiments of this application. The transmitting unit can be a transmitter, a transmitter, a transmitting circuit, etc.

[0112] Figure 5 If the integrated units in the process are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. Storage media for storing computer software products include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory, random access memory, magnetic disks, or optical disks.

[0113] In implementation, each step of the method provided in this embodiment can be completed by integrated logic circuits in the processor or by instructions in software form. The steps of the method disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0114] The processor in this application may include, but is not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, etc., and other computing devices that run software. Each computing device may include one or more cores for executing software instructions to perform calculations or processing. The processor may be a standalone semiconductor chip or integrated with other circuits into a single semiconductor chip. For example, it may be integrated with other circuits (such as encoding / decoding circuits, hardware acceleration circuits, or various bus and interface circuits) to form a System-on-a-Chip (SoC), or it may be integrated as a built-in processor within an ASIC. The ASIC with the integrated processor may be packaged separately or together with other circuits. In addition to the cores for executing software instructions to perform calculations or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), or logic circuits that implement dedicated logic operations.

[0115] The memory in the embodiments of this application may include at least one of the following types: read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; or electrically erasable programmable-only memory (EEPROM). In some scenarios, the memory may also be compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0116] This application also provides a computer-readable storage medium including instructions that, when run on a computer, cause the computer to perform any of the methods described above.

[0117] This application also provides a computer program product containing instructions that, when run on a computer, cause the computer to perform any of the methods described above.

[0118] This application also provides a chip including a processor and an interface circuit. The interface circuit is coupled to the processor. The processor is used to run computer programs or instructions to implement the above-described method. The interface circuit is used to communicate with other modules outside the chip.

[0119] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0120] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, the disclosure, and the appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple components. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0121] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and modifications.

Claims

1. A method for information transmission for an aeronautical obstacle light, characterized in that, The method comprises the following steps: Based on the number of air obstruction lights in each sub-region of the air obstruction light coverage area and the failure rate of the air obstruction lights in each sub-region, a number is assigned to the target terminal corresponding to each air obstruction light; The target terminal corresponding to the air obstruction light is a terminal arranged on the air obstruction light for collecting information of the air obstruction light; A communication period is set, and the communication period is divided into a downlink instruction transmission stage, an uplink data return stage and an event reporting stage. The downlink instruction transmission stage is used for the centralized controller to issue instructions to the target terminal. The uplink data return stage is used for the target terminal to report the status of the air obstruction light to the centralized controller. The event reporting stage is used for the target terminal to report the sudden event of the air obstruction light to the centralized controller; A downlink exclusive communication time slot is set for each target terminal in the downlink instruction transmission stage, and an uplink exclusive communication time slot is set for each target terminal in the uplink data return stage. The time slot length of the exclusive communication time slot is dynamically adjusted by the number data of the target terminal; First indication information is sent to the target terminal. The first indication information is used to indicate the exclusive communication time slot of the target terminal and the communication period.

2. The information transmission method for an aeronautical obstacle light according to claim 1, characterized in that, The method of assigning a number to the target terminal corresponding to each air obstruction light based on the number of air obstruction lights in each sub-region of the air obstruction light coverage area and the failure rate of the air obstruction lights in each sub-region comprises the following steps: The air obstruction light coverage area is divided into multiple sub-regions according to the physical position, and the number of air obstruction lights in each sub-region is obtained; The average failure rate of the terminal in each sub-region in the historical data is counted, and the region weight is calculated; The sub-regions are arranged in descending order according to the region weight. The terminals in the high-weight region are preferentially assigned numbers. In the same sub-region, the terminals are assigned numbers in ascending order of failure rate; When the number of terminals decreases, the numbers of the reduced terminals are kept as idle numbers, which are used to assign to the subsequently added terminals; When the number of terminals increases, the idle numbers are assigned to the added terminals. When there is no available idle number, a new number is assigned to the added terminal; The region weight and the terminal failure rate are periodically recalculated, and the number sequence is updated.

3. The information transmission method for an aeronautical obstacle light according to claim 2, characterized in that, The time slot length of the exclusive communication time slot is dynamically adjusted by the number data of the target terminal, which comprises the following steps: Based on the number of target terminals in each sub-region and the failure rate of the air obstruction lights, combined with the priority weight of the target terminal data type and the channel quality factor, a composite time slot coefficient is calculated. Combined with the minimum guarantee time slot and the number increment coefficient, the exclusive time slot basic length is generated. The minimum guarantee time slot and the number increment coefficient are obtained from the configuration parameter file configured by the centralized controller; The data amount of the target terminal in the next communication period is predicted by using the LSTM model. If the predicted value of the data amount in the next communication period exceeds the burst threshold, a compensation time slot is generated; The sum of the exclusive time slot basic length and the compensation time slot is calculated to determine the final time slot length; When the centralized controller receives an event alarm, the event data preemptive scheduling is activated.

4. The information transmission method for an aeronautical obstacle light according to claim 3, characterized in that, The method of calculating the composite time slot coefficient based on the number of target terminals in each sub-region and the failure rate of the air obstruction lights, combined with the priority weight of the target terminal data type and the channel quality factor, comprises the following steps: According to the data type reported by the target terminal, the priority weight of the data type is dynamically generated; Periodically send test data packets through the RS485 bus, calculate the instantaneous error rate, and convert it into the channel quality factor; Based on the target terminal number i, the failure rate F of the aeronautical obstacle light i , the priority weight P of the target terminal data type i , the channel quality factor Q i , and the number offset δ i , by Calculating the composite time slot coefficient, where N is the total number of terminals, the number offset is calculated by , α, β and γ are configurable weights, and ln(1+N) is the number compensation term.

5. The information transmission method for an aeronautical obstacle light according to claim 4, characterized in that, The data amount of the target terminal in the next communication period is predicted by using the LSTM model, and if the predicted value of the data amount in the next communication period exceeds the burst threshold, a compensation time slot is generated, which includes: Input the historical data amount sequence of the terminal in the last M periods and the fault event of the aviation fault lamp in the same period, and construct a double-channel LSTM model, which fuses the double-channel output predicted value through the attention mechanism; The burst threshold is dynamically set according to the data type reported by the target terminal, wherein the formula for setting the burst threshold is wherein D is The burst threshold, is a historical maximum data amount, is an anti-overfitting decay coefficient, D base is a basic threshold, and μ is a failure rate sensitivity coefficient. When the predicted data volume exceeds the burst threshold, through Generate compensation time slots, where T unit This refers to the single-byte transmission latency.

6. The information transmission method for an aeronautical obstacle light according to claim 5, characterized in that, When the central controller receives the event alarm, the event data preemptive scheduling is activated, which includes: Parse the emergency level identifier in the event alarm, Leve1 level identifier is hardware failure, Leve2 level identifier is parameter out-of-range, and Leve3 level identifier is state anomaly, and set the trigger conditions of the hardware interrupt signal for the Leve1 level identifier, and the software interrupt signal for the Leve2 level identifier and the Leve3 level identifier; Cut the exclusive time slot idle when the terminal has no data transmission demand in the current communication period and the remaining time slot after the terminal transmission into micro time slots, and allocate the number of micro time slots according to the event emergency level identifier; If the single-terminal micro time slot is insufficient, the time slots of adjacent low-priority terminals are merged to form an event transmission block, and the central controller broadcasts a time slot borrowing instruction, the borrowed terminal suspends its own business and forwards event data, and the terminal corresponding to the fault event sends a complete data packet through the aggregated time slot; After the transmission of the fault event is completed, the interrupted terminal continues transmission from the breakpoint, and the central controller adds a compensation time slot for the borrowed terminal.

7. The information transmission method for an aeronautical obstacle light according to claim 6, characterized in that, The downlink instruction transmission stage includes: The central controller broadcasts a control instruction containing the target terminal number through the bus; Each terminal controller listens to the bus signal in real time, extracts the number information in the instruction And match the consistency of the number information in the instruction with the number of the target terminal itself, if the number of the target terminal itself and the number of the instruction do not match, the instruction data is discarded actively; If the number of the target terminal itself and the number of the instruction are consistent, and after verification through the exclusive communication time slot, the instruction is executed.

8. The information transmission method for an aeronautical obstacle light according to claim 7, characterized in that, The uplink data return stage includes: Divide the uplink data return stage into data return period and micro-synchronization period; In the data return period, each terminal sends state data to the central controller through the bus in the exclusive communication time slot; Enter the micro-synchronization period, the central controller checks the integrity of the state data, and initiates a precise retransmission request for the missing terminal; The central controller broadcasts a synchronization calibration signal, and each terminal compensates for the clock drift according to the calibration signal; Generate a period synchronization confirmation mark to trigger the start of the next communication period.

9. The information transmission method for an aeronautical obstacle light according to claim 8, characterized in that, The event reporting stage includes: Set a hierarchical response rule based on the event alarm level: In the Level1 fault event, trigger the hardware interrupt signal, and allow to preempt any terminal exclusive time slot; In the Level2 fault event, trigger the software interrupt signal, and only allow to preempt the exclusive time slot of the same area or low-priority terminal; In the Level3 fault event, trigger the state mark, and only transmit in the idle time slot or at the end of the period; When multiple event alarms are concurrent, preemptive priorities are assigned in descending order of event levels, and events of the same level are arbitrated in ascending order of terminal failure rates.

10. An information transmission device for an aeronautical obstacle light, characterized in that, The device comprises a communication unit and a processing unit; The communication unit is configured to acquire the number of aeronautical obstacle lights in each sub-region of an aeronautical obstacle light coverage area and the failure rates of the aeronautical obstacle lights in each sub-region; The processing unit is configured to assign a number to a target terminal corresponding to each aeronautical obstacle light based on the number of aeronautical obstacle lights in each sub-region of the aeronautical obstacle light coverage area and the failure rates of the aeronautical obstacle lights in each sub-region, wherein the target terminal corresponding to the aeronautical obstacle light is a terminal arranged on the aeronautical obstacle light for collecting information of the aeronautical obstacle light; A communication period is set, and the communication period is divided into a downlink instruction transmission phase, an uplink data return phase and an event reporting phase, the downlink instruction transmission phase is used for the centralized controller to issue instructions to the target terminal, the uplink data return phase is used for the target terminal to report the status of the aeronautical obstacle light to the centralized controller, and the event reporting phase is used for the target terminal to report a sudden event of the aeronautical obstacle light to the centralized controller; A downlink exclusive communication time slot is set for each target terminal in the downlink instruction transmission phase, and an uplink exclusive communication time slot is set for each target terminal in the uplink data return phase, and the time slot length of the exclusive communication time slot is dynamically adjusted by the number data of the target terminal; First indication information is sent to the target terminal, and the first indication information is used to indicate the exclusive communication time slot of the target terminal and the communication period.

Images