Time-triggered protocol network planning method, system, and storage medium for an aviation power system

Abstract

The application provides a time-triggered protocol network planning method, system and storage medium for an aviation power supply system. The network architecture adopts a hardware-level dual-redundancy design, each communication node is configured with two independent TTP physical interfaces and corresponding TTP subcards, and is connected to logically independent TTP A network and TTP B network respectively, so that channel-level fault isolation is realized. The planning method comprises the following steps: classifying messages according to power supply system services and defining transmission periods; initializing a cluster and setting time parameters such as a TDMA period and a cluster period; packing messages with consistent periods and reserving extension bits in a data structure; calculating time slot capacity based on transmission rate, node number and TDMA period, and generating a deterministic message scheduling table. The application guarantees high communication reliability through dual-network redundancy, meets the real-time requirements of various messages such as control and alarm through systematic scheduling, improves the scalability of the network through reserved extension bits, and is suitable for aviation power supply systems with strict communication performance requirements.

Description

Technical Field

[0001] This application relates to the field of aviation electrical technology, and in particular to a time-triggered protocol network planning method, system, and storage medium for aviation power systems. Background Technology

[0002] In recent years, with the increasing integration and intelligence of avionics systems, reliable and real-time communication between internal devices in the avionics power system, as the core energy supply and management unit of the aircraft, has become crucial. Time-Triggered Protocols (TTPs), due to their deterministic timing guarantees and high reliability, have been widely used in avionics networks, especially in safety-critical systems. However, when directly applying TTPs to specific communication scenarios in avionics power systems, existing technical solutions still have significant shortcomings in architectural design and planning methods, making it difficult to fully meet the stringent communication performance requirements of this field.

[0003] Currently, the implementation of communication networks for aviation power systems mainly faces the following technical bottlenecks:

[0004] 1. Inadequate redundancy mechanisms and insufficient reliability assurance: Some existing communication network designs have low redundancy or use only a single communication channel. Even when redundancy is introduced in some solutions, it often remains at the network topology level, failing to achieve deep integration and collaborative design with the underlying TTP controller hardware (such as TTP communication daughter cards). This may lead to data transmission interruptions or switching delays, and cannot provide hardware-level, seamless redundancy protection for the transmission of critical data such as power status monitoring, fault alarms, and load control, thus posing potential risks to flight safety.

[0005] 2. Insufficient fine-grained time synchronization and message scheduling, making real-time performance difficult to guarantee: The TTP protocol is based on the Time Division Multiple Access (TDMA) mechanism, and its communication performance is highly dependent on precise time parameter configuration (such as TDMA cycle, macro clock tick, cluster cycle, etc.). Existing technologies lack systematic scheduling and planning methods for mixed transmission scenarios of multiple message streams (such as millisecond-level control commands, hundreds of millisecond-level alarm information, and seconds-level maintenance data) within aviation power systems. This can easily lead to transmission delays for high-frequency emergency messages due to insufficient time slot allocation, and low-frequency non-real-time messages occupying excessive bandwidth or causing errors due to improper cycle matching, ultimately affecting the real-time performance and determinism of critical operations such as solid-state power controller on / off commands and load management commands.

[0006] 3. Rigid network architecture and message structure with poor scalability: The functions of aviation power systems may face upgrade or expansion requirements throughout the aircraft's lifecycle (such as adding new data loading messages). Existing network planning schemes typically do not reserve expansion space in the message packet structure design, and network configurations and scheduling tables are fixed. Any functional changes or additions to data types may require redesigning the network topology, adjusting the time slot allocation of all nodes, or even changing hardware configurations, resulting in complex, lengthy, and costly upgrade processes that cannot meet the urgent needs of the aviation industry for "full lifecycle upgrades."

[0007] In summary, existing technologies have not yet proposed a systematic network architecture and planning method that can deeply integrate the operational characteristics of aviation power systems with the advantages of the TTP protocol. In particular, effective solutions are lacking in areas such as how to construct hardware-level redundant communication, how to optimize timing parameters to ensure the real-time performance of mixed message flows, and how to design network structures with good forward compatibility. This provides a clear space for technical improvement and a real-world need for the proposal of this invention. Summary of the Invention

[0008] This application provides a time-triggered protocol network planning method, system, and storage medium for aviation power systems, which addresses the problems of imperfect redundancy mechanisms, inaccurate time synchronization and scheduling, and insufficient scalability in existing aviation power system communication networks.

[0009] In a first aspect, this application provides a time-triggered protocol network architecture for an aviation power system, the network architecture being based on a dual-network redundancy design, including:

[0010] Multiple communication nodes cover the aviation power system to enable data interaction between various devices within the system and to report load management information, device power status and alarm information to the avionics network.

[0011] Dual-redundant physical channels: each communication node is configured with two independent TTP physical interfaces, which are constructed through at least two TTP sub-cards to form hardware-level redundancy;

[0012] The dual-redundant logical network includes two independent TTP A networks and a TTP B network. The dual-redundant logical network is associated with the dual-redundant physical channels through a one-to-one configuration relationship to achieve channel-level fault isolation. Preferably, the number of communication nodes is eight.

[0013] Secondly, this application also provides a time-triggered protocol network planning method for an aviation power system, applied to the aforementioned network architecture, the method comprising:

[0014] Message classification and planning steps: Based on the functions and transmission requirements of each device in the aviation power system, classify and plan the messages to be transmitted to form message units, and determine the sending cycle, data length, sender node and receiver node for each type of message.

[0015] Cluster initialization steps: Create a cluster object, configure the network channel, and create node objects; set the TDMA period and the cluster period, wherein the TDMA period does not exceed the shortest update period among all messages, the cluster period does not exceed the longest update period among all messages, and ensures that each node completes at least one transmission and reception of all planned messages within a cluster period;

[0016] Subsystem and message configuration steps: Associate nodes with subsystems and define message types; package message units with consistent update cycles and the same sender and receiver into message packets, and reserve parameter bits in the data structure of the message packets;

[0017] Scheduling and timing planning steps: Based on a preset scheduling table, allocate a defined message transmission time slot to each node within a TDMA cycle, and plan the timing parameters of the transmission frame, including the transmission start time and duration; synchronously define the effective data bit length standard of the transmission frame to ensure that the frame structure and data length sent by each node conform to the scheduling table plan.

[0018] Furthermore, in the message classification and planning steps, the message units include at least several of the following: control message units, indication and alarm message units, power status message units, load management message units, device self-test (BIT) message units, and data loading message units. Specifically, the transmission period of control message units (such as AC power conversion parameters and grid connection control signals) should not exceed 5ms, the transmission period of indication and alarm message units (such as indication and alarm signals and schematic page signals) should not exceed 50ms, and the transmission period of device self-test message units and data loading message units should not exceed 1s.

[0019] Furthermore, in the cluster initialization step, configuring the network channel specifically includes: configuring one TTP physical interface of the node and its corresponding TTP sub-card to access the TTP A network, and configuring the other TTP physical interface and its corresponding TTP sub-card to access the TTP B network, thereby achieving a one-to-one correspondence between the "network and channel".

[0020] Furthermore, in the scheduling and timing planning steps, when constructing the scheduling table, the maximum effective data length L that can be transmitted in each communication time slot is calculated based on the transmission rate v, the number of nodes n, and the TDMA period t. The calculation formula is: L = (t / n) × v. The smaller of the calculation result and the maximum effective data length specified in the protocol (e.g., 240 bytes) is taken as the basis for designing the size of the reserved effective data space, so as to optimize bandwidth utilization and reserve space for future expansion.

[0021] Furthermore, the method also includes a message frame construction step: assembling the valid data to be sent by each node into packets according to the TTP data frame format. The TTP data frame format sequentially includes: a frame header, a controller status field, an application data field, and a checksum field. The application data field carries the message packet, and the checksum field uses a CRC checksum algorithm. The message packet carried in the application data field contains parameter bits reserved for future functional upgrades.

[0022] Thirdly, this application also provides an aviation power system, the system comprising the aforementioned time-triggered protocol network architecture for aviation power systems, and the communication nodes in the system communicating in accordance with the aforementioned time-triggered protocol network planning method for aviation power systems.

[0023] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-described time-triggered protocol network planning method for an aviation power system.

[0024] Compared with the prior art, the technical solution provided by the present invention has the following significant advantages:

[0025] 1. Significantly Enhanced Redundancy and Reliability: Through a deep collaborative design of "dual hardware channels (dual TTP daughter cards) + dual logical networks (A / B networks)," dual redundancy from the physical layer to the protocol layer is achieved. This design effectively isolates single-point network failures. Calculations show that the network disconnection rate is lower than 8.11832E-05, and the transmission success rate of critical data (such as power control commands and emergency alarms) can reach 100%, fully meeting the extremely high reliability requirements of aviation power systems for communication.

[0026] 2. Real-time performance and determinism are guaranteed: Through systematic message classification and business-demand-based period definitions, combined with constrained planning of core time parameters such as TDMA period and cluster period, extremely low latency (≤5ms) of high-frequency control commands and strict determinism of all message transmission periods (period deviation ≤5%) are ensured. This resolves the real-time conflict problem in mixed service flow scenarios and provides a communication foundation for precise control of the power system.

[0027] 3. Enhanced Network Scalability and Maintainability: The design of reserving parameter bits in the message packet structure enables the system to smoothly support the expansion of 3-5 new data types in the future without refactoring the existing network architecture, scheduling tables, or hardware connections. It is estimated that this method can reduce the cost of subsequent function upgrades by more than 60%, significantly improving the economy and flexibility of the aviation power system throughout its entire lifecycle.

[0028] 4. Highly Efficient and Collaborative Planning Process: The systematic planning method proposed in this invention forms a logically rigorous closed-loop process from message analysis to scheduling table generation. Through technologies such as clustered databases, seamless data integration and automatic verification across all design stages are achieved, effectively reducing human error rates and improving the efficiency and first-time success rate of network planning. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0030] Figure 1 This is a schematic diagram of the TTP data frame format used in the embodiments of this application;

[0031] Figure 2 This is a flowchart of a TTP network planning method for an aviation power system provided in an embodiment of this application;

[0032] Figure 3 This is a schematic representation of the TTP network message scheduling generated in the embodiments of this application. Detailed Implementation

[0033] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0034] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein.

[0035] This invention provides a time-triggered protocol network architecture for aviation power systems. This architecture is based on a dual-network redundancy design, including multiple communication nodes, dual-redundant physical channels, and dual-redundant logical networks. The multiple communication nodes cover the aviation power system, enabling data interaction between devices within the system and reporting load management information, device power status, and alarm information to the avionics network. Each communication node is configured with two independent TTP physical interfaces, constructed using at least two TTP sub-cards to form hardware-level redundancy. The dual-redundant logical network includes independent TTP A and TTP B networks. The dual-redundant logical network and the dual-redundant physical channels are associated through a one-to-one configuration relationship to achieve channel-level fault isolation. In other words, the hardware layer equips each communication node (a total of 8) with two independent TTP communication sub-cards, thus forming two independent 4Mbps physical communication channels (Channel A and Channel B). Based on the hardware channels, two completely independent TTP networks are logically constructed: TTP A and TTP B. Each node's Channel A is fixedly connected to Network A, and Channel B is fixedly connected to Network B. Under normal circumstances, the two networks operate in parallel, transmitting the same data. When any network or channel fails, the other network can seamlessly take over all communication tasks, achieving fault isolation and uninterrupted communication. This invention employs a deep collaborative design of "hardware dual channels (dual TTP daughter cards) + logical dual networks (A / B networks)," achieving dual redundancy from the physical layer to the protocol layer. This design effectively isolates single-point network failures. Calculations show that the network disconnection rate can be lower than 8.11832E-05, and the transmission success rate of critical data (such as power control commands and emergency alarms) can reach 100%, fully meeting the extremely high reliability requirements of aviation power systems for communication.

[0036] For example, the aviation power system includes eight key devices as communication nodes, such as the generator controller (GCU), busbar power controller (BPCU), and remote power distribution unit (RPDU).

[0037] For example, refer to Figure 1 The frame format of the TTP message in this embodiment is described in detail, including:

[0038] Frame header: Indicates the frame type and mode change request field;

[0039] Controller status word: 12 bytes, used to describe the cluster status of the TTP controller relative to global time, cluster location, and member status;

[0040] Application data: The length is related to the message type and can carry aviation power business data such as power status and controller commands, and reserves extension bits to support the addition of new data types;

[0041] Double verification: The CRC check algorithm is used to ensure the integrity and correctness of data transmission.

[0042] For example, refer to Figure 3 The number of communication nodes is 8. For example... Figure 3 The table shown is a two-dimensional matrix. The vertical axis represents the 16 rounds of time triggering cycles (Rounds 1-16, representing a 40ms cluster cycle), and the horizontal axis represents 8 time slots (Slots 0-7, corresponding to 8 nodes Node1-Node8). Rectangular blocks mark the time slot occupancy status of each node in a specific round (rectangular parts indicate occupied slots, and blank areas indicate idle slots). White, black, and gray rectangles represent TTP message frames; white rectangles represent the frame header, controller status, and checksum 1, while black and gray rectangles represent the application data. This table uniquely determines when and for how long each node sends a message, avoiding bus conflicts and ensuring deterministic communication.

[0043] This invention provides a time-triggered protocol network planning method for aviation power systems, applied to the aforementioned network architecture. The method includes:

[0044] Message Classification and Planning Steps: Based on the functions and transmission requirements of each device in the aviation power system, the messages to be transmitted are classified and planned to form message units. The transmission cycle, data length, sender node, and receiver node for each type of message are determined. A message unit should include at least several of the following: control message units, indication / alarm message units, power status message units, load management message units, device self-test (BIT) message units, and data loading message units. Specifically, the transmission cycle of control message units (such as AC power conversion parameters and grid connection control signals) should not exceed 5ms, the transmission cycle of indication / alarm message units (such as indication / alarm and schematic page signals) should not exceed 50ms, and the transmission cycle of device self-test message units and data loading message units should not exceed 1s.

[0045] Cluster initialization steps: Create a cluster object, configure network channels, and create node objects; set the TDMA period and cluster period, wherein the TDMA period does not exceed the shortest update period among all messages, and the cluster period does not exceed the longest update period among all messages, and ensures that each node completes at least one transmission and reception of all planned messages within a cluster period. Configuring the network channel specifically includes: configuring one TTP physical interface and its corresponding TTP sub-card of a node to access the TTPA network, and configuring the other TTP physical interface and its corresponding TTP sub-card to access the TTP B network, thereby achieving a one-to-one correspondence between "network" and "channel".

[0046] Subsystem and message configuration steps: Associate nodes with subsystems and define message types; package message units with consistent update cycles and the same sender and receiver into message packets, and reserve parameter bits in the data structure of the message packets.

[0047] Scheduling and timing planning steps: Based on a preset scheduling table, a defined message transmission time slot is allocated to each node within a TDMA cycle, and the timing parameters of the transmission frame are planned. These timing parameters include the transmission start time and duration. A standard for the effective data bit length of the transmission frame is defined synchronously to ensure that the frame structure and data length sent by each node conform to the scheduling table plan. Specifically, when constructing the scheduling table, the maximum effective data length L that can be transmitted in each communication time slot is calculated based on the transmission rate v, the number of nodes n, and the TDMA cycle t. The calculation formula is: L = (t / n) × v. The smaller of the calculation result and the maximum effective data length specified in the protocol (e.g., 240 bytes) is used as the basis for designing the size of the reserved effective data space to optimize bandwidth utilization and leave room for future expansion.

[0048] For example, the scheduling and timing planning steps further include a message frame construction step: assembling the valid data to be sent by each node into packets according to the TTP data frame format. The TTP data frame format sequentially includes: a frame header, a controller status field, an application data field, and a checksum field. The application data field carries the message packet, and the checksum field uses a CRC checksum algorithm. The message packet carried in the application data field contains parameter bits reserved for future functional upgrades.

[0049] Reference Figure 2 The flowchart shown below provides a detailed explanation of the network planning process in this embodiment.

[0050] Step S1: Message classification and planning.

[0051] First, a comprehensive review of all data requiring interaction within the power system is conducted. Based on the urgency and characteristics of the business, different types of messages from the aviation power system are categorized into message units, and the sending cycle, data length, sender node, and receiver node for each type of message are determined.

[0052] Among them, the control message unit includes, for example, the grid connection control signal between the GCU and BPCU, and the power supply conversion parameters between the BPCUs. Real-time performance is required to be extremely high, with an update cycle of ≤5ms.

[0053] Alarm and warning message units: such as schematic diagram signals and fault indications reported by the BPCU to the avionics alarm system via RPDU. Medium real-time performance is required, with an update cycle ≤50ms.

[0054] Power status message units: such as device self-test (BIT) status, configuration, data loading commands, etc. Real-time requirements are low, with an update cycle of ≤1 second. Simultaneously, information such as the sender, receiver, and data length of each message is recorded.

[0055] Step S2: Cluster initialization.

[0056] Use a TTP network planning tool (such as TTEPlan) to create a new cluster. Based on the data from step S1, set the core time parameters:

[0057] TDMA Period: This period determines the most basic time slot division granularity of the network. To ensure that the shortest period (5ms) message has a chance to be sent in each period, and to guarantee the timeliness and orderliness of message transmission, the TDMA period is set to ≤5ms, and in this embodiment it is set to 2.5ms.

[0058] Cluster cycle: Within this cycle, at least one transmission of all message types should be completed to ensure the timeliness and orderliness of message transmission. Based on the longest cycle (1s) and the total number of messages, the cluster cycle is determined to be 16 TDMA cycles, or 40ms. This ensures that 25 complete cycles can be completed within 1 second, satisfying the cycle requirements of all messages.

[0059] Node and Channel Configuration: Create 8 node objects (Node1~Node8) in the tool. Configure two network interfaces for each node and specify that it belongs to TTP A network and TTP B network respectively.

[0060] Step S3: Scheduling and Timing Planning.

[0061] Multiple messages from the same sender, destined for the same receiver, and with the same update cycle are grouped into a single "message packet." For example, multiple status signals that the BPCU needs to send can be packaged together.

[0062] Key design considerations: When defining the data structure of the message packet, in addition to including all data fields required by the current business logic, a certain number of bytes are reserved at the end of the application data area as extension parameter bits. This supports future upgrades and prevents the reconstruction of the existing network plan due to functional upgrades. The reserved length is determined through calculation.

[0063] Frame format: Standard TTP frame format is used, refer to Figure 1The diagram showing the TTP data frame format details the frame format of the TTP message in this embodiment, including: Frame header: indicating the frame type and mode change request field; Controller status word: 12 bytes, used to describe the cluster status of the TTP controller relative to global time, cluster location, and member status; Application data: length related to the message type, can carry aviation power service data such as power status and controller commands, and reserves extension bits to support new data types; Dual verification: using the CRC check algorithm to ensure the integrity and correctness of data transmission.

[0064] Time slot capacity calculation: Given a network transmission rate v = 4Mbps, number of nodes n = 8, and TDMA cycle t = 2.5ms. Using the formula L = (t / n) × v, calculate the maximum application data length that each node can transmit in a time slot within one TDMA cycle. Substituting the values: Single time slot duration = 2.5ms / 8 = 312.5μs. Transmittable data bits = 312.5μs * 4Mb / s = 1250 bits ≈ 156.25 bytes. Comparing this to the typically specified 240-byte application data limit in the TTP protocol, the smaller value of 156 bytes is taken as the theoretical maximum value of the effective data length per time slot in this embodiment.

[0065] Reserved space design: When packaging the message packet in step S3, ensure that its length is less than 156 bytes. The difference between 156 bytes and the actual data length is used as reserved space for future expansion of the message packet.

[0066] Generating the scheduling table: Based on the above constraints, a planning tool is used for automated arrangement and optimization to generate the final TTP network message scheduling table, such as... Figure 3 As shown in the diagram, this table is a two-dimensional matrix. The vertical axis represents the 16 rounds of time triggering cycles (Rounds 1-16, representing a 40ms cluster cycle), and the horizontal axis represents 8 time slots (Slots 0-7, corresponding to 8 nodes Node1-Node8). Rectangular blocks mark the time slot occupancy status of each node in a specific round (rectangular portions indicate occupied slots, and blank portions indicate idle slots). White, black, and gray rectangles represent TTP message frames; white rectangles represent the frame header, controller status, and checksum 1, while black and gray rectangles represent the application data portion. This table uniquely determines when and for how long each node sends a message, avoiding bus conflicts and ensuring deterministic communication.

[0067] The generated configuration files (containing cluster parameters, scheduling tables, message descriptions, etc.) are downloaded to the TTP controllers of the eight nodes. After the system powers on, each node synchronously sends data on both the A and B networks according to the scheduling table. The receiver verifies and selects the best data from both networks, thereby achieving highly reliable communication.

[0068] For example, the network implemented in this embodiment is tested and verified:

[0069] Redundancy test: Simulating the disconnection of any TTP sub-card or physical link of any node, the network disconnection rate is less than 8.11832E-05, the transmission success rate of critical data (such as power alarm) reaches 100%, which meets the high reliability requirements of aviation power supply. The system communication is uninterrupted, all critical messages are received normally, and the switching process is imperceptible, which verifies the effectiveness of hardware-level redundancy.

[0070] Real-time performance test: Through parameter constraints of TDMA cycle and cluster cycle, the transmission delay of high-frequency messages (such as control commands and fault information) is 3.2ms (<5ms). The scheduling table after network planning makes the message cycle deviation less than 2% (<5%), which meets the real-time requirements of control and alarm reporting.

[0071] Extensible simulation: The reserved parameter bits in the message packet support the expansion of 3-5 new data types without reconstructing the network. To simulate adding a new power quality monitoring data, the new field can be added directly using the reserved space in the message packet. Only the application layer software configuration needs to be updated. The network scheduling table and underlying configuration do not need any changes. The upgrade is convenient and the upgrade cost is reduced by more than 60%.

[0072] This invention also provides an aviation power system, which includes the above-described time-triggered protocol network architecture for aviation power systems. The communication nodes in the system communicate according to the above-described time-triggered protocol network planning method for aviation power systems, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0073] This invention also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the steps of the above-described time-triggered protocol network planning method for aviation power systems and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0074] In summary, this invention provides a complete, highly reliable, real-time, and scalable TTP network communication solution for aviation power systems through synergistic innovation in architecture and methodology, and has promising prospects for engineering applications.

[0075] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A network planning method for a time-triggered protocol in an aviation power system, applied to a network architecture for a time-triggered protocol in an aviation power system, the network architecture being based on a dual-network redundancy design, comprising: Multiple communication nodes cover the aviation power system to enable data interaction between various devices within the system and to report load management information, device power status and alarm information to the avionics network. Dual-redundant physical channels: each communication node is configured with two independent TTP physical interfaces, which are constructed through at least two TTP sub-cards to form hardware-level redundancy; A dual-redundant logical network, comprising independent TTP A network and TTP B network, wherein the dual-redundant logical network and the dual-redundant physical channels are associated through a one-to-one configuration relationship to achieve channel-level fault isolation, characterized in that the method includes: Message classification and planning steps: Based on the functions and transmission requirements of each device in the aviation power system, classify and plan the messages to be transmitted to form message units, and determine the sending cycle, data length, sender node and receiver node for each type of message. Cluster initialization steps: Create a cluster object, configure the network channel, and create node objects; set the TDMA period and the cluster period, wherein the TDMA period does not exceed the shortest update period among all messages, the cluster period does not exceed the longest update period among all messages, and ensures that each node completes at least one transmission and reception of all planned messages within a cluster period; Subsystem and message configuration steps: Associate nodes with subsystems and define message types; package message units with consistent update cycles and the same sender and receiver into message packets, and reserve parameter bits in the data structure of the message packets; Scheduling and timing planning steps: Based on a preset scheduling table, allocate a defined message transmission time slot to each node within a TDMA cycle, and plan the timing parameters of the transmission frame, including the transmission start time and duration; synchronously define the effective data bit length standard of the transmission frame to ensure that the frame structure and data length sent by each node conform to the scheduling table plan.

2. The time-triggered protocol network planning method for aviation power systems according to claim 1, characterized in that, In the message classification and planning steps, the message unit includes at least a variety of control message units, indication and alarm message units, power status message units, load management message units, device self-test message units, and data loading message units; wherein, the transmission period of the control message unit is no more than 5ms, the transmission period of the indication and alarm message unit is no more than 50ms, and the transmission period of the device self-test message unit and the data loading message unit is no more than 1s.

3. The time-triggered protocol network planning method for aviation power systems according to claim 1, characterized in that, In the cluster initialization step, configuring the network channel specifically includes: configuring one TTP physical interface and the corresponding TTP sub-card of the node to access the TTP A network, and configuring the other TTP physical interface and the corresponding TTP sub-card to access the TTP B network.

4. The time-triggered protocol network planning method for aviation power systems according to claim 1, characterized in that, In the scheduling and timing planning step, when constructing the scheduling table, the maximum effective data length L that can be transmitted in each communication time slot is calculated based on the transmission rate v, the number of nodes n, and the TDMA period t. The calculation formula is: L=(t / n)×v; The smaller of the calculation result and the maximum length of valid data specified in the protocol will be used as the basis for designing the size of the reserved valid data space.

5. The time-triggered protocol network planning method for aviation power systems according to claim 1, characterized in that, The method further includes a message frame construction step: assembling the valid data to be sent by each node into packets according to the TTP data frame format, wherein the TTP data frame format includes, in sequence: a frame header, a controller status field, an application data field, and a verification field; wherein the application data field is used to carry the message packet, and the verification field adopts the CRC check algorithm.

6. The time-triggered protocol network planning method for aviation power systems according to claim 5, characterized in that, The message packets carried in the application data fields contain parameter bits reserved for future function upgrades.

7. An aviation power system, characterized in that, Furthermore, the communication nodes in the system communicate in accordance with the time-triggered protocol network planning method for aviation power systems as described in any one of claims 1 to 6.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the time-triggered protocol network planning method for an aviation power system as described in any one of claims 1 to 6.

Images