Discrete event simulation method for ARINC664 time management function
By constructing a network environment simulator using discrete event simulation methods, the complexity of simulating the ARINC664 time management function was solved, and the evaluation and verification of high-integrity data transmission were realized, improving simulation efficiency and confidence.
Patent Information
- Application Number
- CN202311255299.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-09-26
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-09-26
AI Technical Summary
Existing technologies for simulating ARINC664 time management functions in aviation Ethernet suffer from problems such as large development workload, complex simulation, and difficulty in supporting the evaluation and verification of high-integrity data transmission.
A discrete event simulation method is adopted, and a network environment simulator is built through an event manager, a terminal clock source module, a time management terminal module, a time agent terminal module, a data transmission path module, and a statistics management module. This enables simulation of high-integrity time management functions and supports time deviation calculation and evaluation.
It improves the efficiency and confidence of time management function simulation, can realistically simulate the operation scenario of time management function, and supports the evaluation and confirmation of high-integrity data transmission.
Smart Images

Figure CN117319221B_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of data communication and relates to a discrete event simulation method for ARINC664 time management function, which evaluates and confirms the network time management function. Background Technology
[0002] Typical avionics systems in civil aircraft primarily employ a star-shaped ARINC664 network to support data communication between different network nodes. The network transmission time delay performance must meet system design requirements. In the network design of typical large aircraft, time management protocols are mainly used for soft time synchronization of various network terminal nodes, supporting system evaluation of network performance indicators. Terminal nodes communicate data based on transmission service mechanisms such as send / receive and request / response. Data transmission errors during this process can have serious consequences for upper-layer system applications; therefore, high-integrity data transmission functionality between end-to-end channels is required. In high-integrity data transmission functionality, time integrity is related to the time delay performance of terminal nodes during transmission. Verification of time integrity first requires establishing a time management function. The overall system architecture of the ARINC664 time management function is as follows: Figure 1 Time management function modeling, such as Figure 2 The time management endpoint is a network node connected to the switch network. It has a time management application installed on it, controlling the time management process and responsible for constructing and sending time request messages. The time agent endpoint is also a node in the network, connected to the switch network. It has a time agent application installed on it, responsible for receiving time request messages and constructing and sending time response messages. Aviation Ethernet uses ARINC664 as the communication protocol specification, constructing virtual links from the management endpoint to the agent endpoint, and virtual links from the agent endpoint to the management endpoint. Each virtual link has its own queue. The scheduler at the sending end, based on the minimum transmission interval set in the configuration, uses redundancy management to send each data packet in the queue to the receiving end through channels A and B respectively. When data is sent to the receiving end of the agent endpoint through channels A and B, the agent endpoint performs integrity checks on the data, removes erroneous data packets, performs redundancy elimination, ignores packets with duplicate content, and then hands it over to the upper-layer agent application. After completing the process in the time management protocol, record the clock source time T1 when the time management end sends the time request message, the clock source time T2 when the time agent end receives the time response message, the clock source time T3 when the time agent end sends the time response message, and the clock source time T4 when the time management end receives the time response message. Finally, calculate the time deviation, complete the time integrity verification, and support high integrity data transmission.
[0003] Traditional application layer protocol design for network systems mainly includes two approaches. The first approach is to customize and develop network protocols and time management protocols based on commercial Ethernet simulation environments. Due to the lack of protocol communication modules for dedicated avionics networks, the workload of secondary development is large, and the large amount of redundant simulation data leads to long execution times and difficulties in data screening. The second approach is to develop and test protocols based on real network devices. The main problem is that the internal structure of the devices makes the test scenarios complex and difficult to support system-level evaluation. Summary of the Invention
[0004] The purpose of this invention is to provide a discrete event simulation method for ARINC664 time management functions. Based on discrete event simulation control technology, a network environment simulator is constructed, and high-integrity time management function simulation is implemented on network nodes. It supports the analysis of time management protocols between asynchronous terminals and the evaluation of the impact factors of time deviation algorithms, providing verification data for subsequent confirmation and evaluation of time management functions, so as to support terminals with high integrity to perform time integrity checks during data transmission.
[0005] The objective of this invention is achieved through the following technical solution:
[0006] A discrete event simulation method for ARINC664 time management functionality is implemented through an event manager, a terminal clock source module, a time management terminal module, a time proxy terminal module, a data transmission path module, and a statistics management module, comprising the following steps:
[0007] Step 1: Decompose the ARINC664 time management function into discrete events executed by the time management module, the data transmission path module, and the time agent module;
[0008] Step 2: Mark each discrete event with an execution timestamp;
[0009] Step 3: The event manager queues discrete events according to their execution timestamps to form an event queue. It continuously selects the first event from the event queue and hands it over to the time management module, data transmission path module, or time proxy module for execution. The current simulation time is the execution timestamp of the event. After one event is completed, the next event is executed immediately, and the time inside the event manager is also changed to the execution timestamp of the next event.
[0010] Step 4: The terminal clock source module provides the terminal clock source time to the time management module and the time agent module. The time management module and the time agent module record the sending request timestamp T1 for sending time request messages, the receiving request timestamp T2 for receiving time request messages, the sending response timestamp T3 for sending time response messages, and the receiving response timestamp T4 for receiving time response messages. The statistics management module is responsible for recording data related to the time management function.
[0011] The beneficial effects of this invention are as follows:
[0012] The discrete event simulation method for ARINC 664 time management function is based on the ARINC 664 protocol of aviation Ethernet. It uses discrete time simulation technology to establish a simulation environment for time management function. By simulating network operation scenarios and data cycle transmission, it obtains time characteristic data of time management function under specific scenarios, supports the calculation and analysis of time deviation between terminals, and realizes the confirmation of the algorithm for calculating time deviation of network nodes in data transmission and the high integrity index of the network.
[0013] The discrete event simulation method for ARINC664 time management functions accelerates the simulation efficiency of time management functions by customizing and simplifying network communication topology and node application models and using discrete event control. By unifying the simulation time settings and clock source drift design, it can more realistically simulate the operation scenario of time management functions, making the confidence of evaluation and confirmation higher. Attached Figure Description
[0014] Figure 1 The overall system architecture for ARINC664 time management functionality.
[0015] Figure 2 This is a schematic diagram of a network model for time management functions.
[0016] Figure 3 This is a schematic diagram of the discrete event scheduling process.
[0017] Figure 4 This is a flowchart illustrating the functions of the time management module.
[0018] Figure 5 This is a flowchart of the time agent's functions. Detailed Implementation
[0019] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments.
[0020] This embodiment illustrates a discrete event simulation method for ARINC664 time management functionality. It is implemented through an event manager, a terminal clock source module, a time management module, a time proxy module, a data transmission path module, and a statistics management module, requiring the following six design elements:
[0021] (1) Define data packets
[0022] In discrete event simulations, data packets do not need to have the same realistic data packet structure as in actual networks. Each data packet is a single object instance, and the fields in the packet header are represented by member variables of the class. The member variables of the packet header are as follows:
[0023] 1) Message types: including time request messages, time response messages, and timestamp list messages;
[0024] 2) Channel, indicating whether the message comes from channel A or channel B;
[0025] 3) The sending end: Which Elasticsearch (ES) system did the message originate from?
[0026] 4) Sending timestamp: The sending system time when the message is sent at the application layer;
[0027] 5) At the receiving end, which ES (Elasticsearch) system the message is sent to;
[0028] 6) Receive timestamp: The system time of the receiving end when the application layer receives the message;
[0029] 7) Serial number, confirming the order of message confirmation data packets, ensuring the integrity of data transmission order;
[0030] 8) The data packet size is the sum of the header size and the content size, and must comply with the ARINC664 limit on data packet size;
[0031] The data packet content carries the corresponding data according to the message type. Time request messages carry the sending request timestamp T1 and the sequence number of the request / response message (see 7 above), time response messages carry the sending request timestamp T1 and the receiving request timestamp T2 of the response time request message, and timestamp list messages carry the sending request timestamp T1 and the receiving request timestamp T2 of the time request message, and the sending response timestamp T3 and the receiving response timestamp T4 of the response time request message.
[0032] The timestamp T1 for sending the request is the time when the time request message arrives at the head of the sending queue, as calculated by the time management module.
[0033] The timestamp T2 for receiving the request is the time when the time agent module receives the time request message sent by the time management module.
[0034] The response timestamp T3 is the time when the response message arrives at the head of the sending queue, calculated by the time agent module.
[0035] The time management module receives the time response message sent by the time agent module, which is the T4 response timestamp.
[0036] (2) Terminal clock source module
[0037] The time management module and the time proxy module maintain their own terminal time source module. The terminal time source module provides an interface to the time management module and the time proxy module to obtain the terminal time source. The terminal time source is calculated using the simulation time source stored in the time management module and the time proxy module, and the time drift rate stored in the time management module. The calculation method is as follows:
[0038] Terminal time source time = Simulation current time + Simulation actual elapsed time * Time drift rate
[0039] When the time management module and the time proxy module need to obtain the current terminal time source, they need to use the interface provided by the terminal time source module. For example, the timestamps T1 to T4 within the data packet are all obtained from the terminal time source module. Furthermore, to meet the needs of subsequent statistical management function modules, the terminal's internal time source information and the actual simulated time source will also provide interfaces for time source data acquisition.
[0040] (3) Time Management Module
[0041] The time management module relies on an application installed on the end system. It simulates the sending and receiving of data packets by the time management terminal based on the event manager's scheduling. The workflow of the time management module is as follows: Figure 4 :
[0042] When executing the creation time request message event, the time request message is packaged according to the data packet structure defined above, and a sequence number tag is added according to the order of the data packets; the execution time of the send time request message event is calculated based on the actual time of creating the time request message according to the ARINC664 data packet format, the actual time of the time request message being queued in the sending queue for sending, and the multicast send time request message events are recursively added to the event queue;
[0043] When the time request message event is executed, it indicates that the time request message data packet has finished queuing in the sending queue and has reached the head of the sending queue. After obtaining the terminal time source from the terminal clock source module, the time management module fills the sending timestamp field of the request message data packet as the sending timestamp T1, and sends the time request message data packet to the A and B channels of the data transmission path module. The execution time of the receiving time request message event is calculated based on the actual network transmission delay and the message receiving clock error of the time agent (including clock drift and stamping error), and the receiving time request message event is added to the event queue.
[0044] When executing the receive time response message event, the time management module receives time response messages from multiple time agent modules via channels A and B of the data transmission path module. It uses the send request timestamp T1 and receive request timestamp T2 stored in the packet content of the first arriving time response message data packet, and the send response timestamp T3 and receive response timestamp T4 in the packet header of the time response message data packet. If no time response message is received on a certain channel, or if multiple duplicate time response messages are received, the time management module will call the relevant interface of the statistics management module to record the event.
[0045] In addition, the time management module also needs to construct a timestamp list message event. The timestamp list consists of four timestamp lists T1 to T4 for itself and its corresponding agent, which are sent to the corresponding time agent module when the timestamp list message event is executed.
[0046] In each time management cycle, regardless of whether the corresponding time response message has been received, the time management module will start sending timestamp list messages one second after sending the time request message.
[0047] (4) Time Agent Module
[0048] The time proxy module is implemented through an application installed on the end system. It simulates the response behavior of the time proxy based on the event manager's scheduling. The workflow of the time proxy module is as follows: Figure 5 .
[0049] When executing the receive time request message event, the time agent module receives the time request message transmitted from the A and B channels of the data transmission path module, and collects the sending request timestamp T1 and receiving request timestamp T2 of the time request message.
[0050] When executing the creation time response message event, the time response message is packaged according to the data packet structure defined above, and a sequence number tag is added according to the order of the data packets. The time response message is added to the data packet sending queue of the time agent module. The execution time of the sending time response message event is calculated based on the actual time of creating the time response message according to the ARINC data packet format and the actual time of waiting for the time response message to be sent in the sending queue. The sending time response message event is then added to the event queue.
[0051] When executing the sending time response message event, the time agent module fills in the sending response timestamp T3 in the sending timestamp field of the time response message data packet, sends the time response message data packet to the A and B channels of the data transmission path module, and calculates the execution time of the receiving time response message event based on the network transmission delay and the message receiving clock error of the time management terminal (including clock drift and stamping error), and adds the receiving time response message event to the event queue.
[0052] (5) Data transmission path module
[0053] The data transmission path module is used to simulate the delay of each message in channels A and B, and to record the timestamp of time request messages arriving at the transmission path and the timestamp of time response messages arriving at the transmission path.
[0054] When executing the transmission time request message event, the timestamp of when the time request message data packet arrives at the transmission path is recorded, and the packet waits for a fixed transmission delay on the A / B channel transmission path according to the data packet channel setting. After adding the clock error, it is passed to the time agent module.
[0055] When executing the transmission time response message event, the timestamp of when the time response message data packet arrives at the transmission path is recorded, and the packet waits for a fixed transmission delay on the A / B channel transmission path according to the data packet channel setting. After adding the clock error, the packet is then transmitted to the time management module.
[0056] The timestamps recorded by the data transmission path module are used to confirm the protocol as a whole. By analyzing and comparing the timestamp deviations between T1 and T2, the timestamp deviations between T3 and T4, and the timestamp list messages, the impact of transmission path delay on the protocol can be evaluated as a whole.
[0057] (6) Statistical Management Module
[0058] The statistics management module is responsible for recording data related to the time management function, including data sent and received through the statistics channel, packet loss and errors in received data, and time offset results and time offsets. The specific data that needs to be recorded is as follows:
[0059] 1) Execute a round of time management function, and compile a list of timestamps of data transmission recorded by the time management module, the current actual time source, and the time source of the management terminal.
[0060] 2) Execute a round of time management function to count the current actual simulation time source and the terminal time source maintained by each time agent module.
[0061] 3) Count the number of unresponsive channels A and B recorded by the time management module and the time agent module.
[0062] 4) The time management module and the time agent module record the number of repeated responses for channel A and channel B.
[0063] 5) The statistics time management module records the sender, the recipient, and the timestamp of the dropped data packets.
[0064] 6) The statistics time management module records the sender, recipient, and timestamp of the erroneous data packets.
[0065] By designing the above six parts, an avionics system network architecture is formed, which interacts with the discrete event manager to create a discrete event network simulation environment. Initial parameters are then input into the simulation environment through discrete event execution timestamp parameter configuration and simulation data acquisition to simulate network data transmission. Secondly, based on the time management function, a discrete event scheduling process is designed as follows: Figure 3 As shown, the transmission of data packets in the network is completed; finally, the simulation data results are output for subsequent protocol analysis and algorithm confirmation.
[0066] This implementation case demonstrates a discrete event simulation method for ARINC664 time management functionality through the following four steps.
[0067] Step 1: Decompose the ARINC664 time management function into discrete events executed by the time management module, the data transmission path module, and the time agent module.
[0068] Taking a time management cycle as an example, where the time management terminal sends a time request message to a time agent and receives a time response message from the time agent, this process can be broken down into the following events:
[0069] 1) Time Management Module
[0070] This includes the following four events:
[0071] ① Creation time request message
[0072] ② Send a time request message
[0073] ③ Receive time response message
[0074] ④ Send timestamp list message
[0075] 2) Data transmission path module
[0076] This includes two events:
[0077] ① Transmission Time Request Message
[0078] ② Transmission time response message
[0079] 3) Time Agent Module
[0080] This includes the following three events:
[0081] ① Receive time request message
[0082] ② Create a time-based response message
[0083] ③ Send time response message
[0084] Step 2: Mark each discrete event with an execution timestamp.
[0085] The simulation process of time management is described, defining a method for calculating execution timestamps and recording the execution timestamps of discrete events to analyze the issue of time asynchrony between different terminals. See the table below:
[0086]
[0087] Step 3: The event manager queues discrete events according to their execution timestamps, forming an event queue. It continuously selects the first event from the queue and assigns it to the time management module, data transmission path module, or time proxy module for execution. The current simulation time becomes the event's execution timestamp. After one event is completed, the next event is executed immediately, and the event manager's internal time is updated to reflect the next event's execution timestamp.
[0088] The discrete event scheduling process of the event manager is as follows: Figure 3 As shown, the simulation of the real time management process can be completed by continuously executing discrete events in the event queue.
[0089] Step 4: The terminal clock source module provides the terminal clock source time to the time management module and the time agent module, so that the time management module and the time agent module can record the sending request timestamp T1 of the time request message, the receiving request timestamp T2 of the time request message received by the time agent module, the sending response timestamp T3 of the time response message sent by the time agent module, and the receiving response timestamp T4 of the time response message received by the time management module. The statistics management module is responsible for recording the data related to the time management function.
[0090] The above four steps record timestamps T1, T2, T3, and T4, which are used to verify the corresponding time deviation algorithm in the time management function.
[0091] It is understood that those skilled in the art can make equivalent substitutions or modifications to the technical solution and inventive concept of the present invention, and all such substitutions or modifications should fall within the protection scope of the appended claims.
Claims
1. A discrete event simulation method for ARINC664 time management functions, implemented through an event manager, a terminal clock source module, a time management terminal module, a time proxy terminal module, a data transmission path module, and a statistical management module, characterized in that... Includes the following steps: Step 1: Decompose the ARINC664 time management function into discrete events executed by the time management module, the data transmission path module, and the time agent module; Step 2: Mark each discrete event with an execution timestamp; Step 3: The event manager queues discrete events according to their execution timestamps to form an event queue. It continuously selects the first event from the event queue and hands it over to the time management module, data transmission path module, or time proxy module for execution. The current simulation time is the execution timestamp of the event. After one event is completed, the next event is executed immediately, and the time inside the event manager is also changed to the execution timestamp of the next event. Step 4: The terminal clock source module provides the terminal clock source time to the time management module and the time agent module, so that the time management module and the time agent module can record the sending request timestamp T1 of the time request message, the receiving request timestamp T2 of the time request message received by the time agent module, the sending response timestamp T3 of the time response message sent by the time agent module, and the receiving response timestamp T4 of the time response message received by the time management module. The statistics management module is responsible for recording the data related to the time management function. Wherein: The terminal time source time provided by the terminal clock source module is: Terminal time source time = Simulation current time + Simulation actual elapsed time * Time drift rate; The workflow of the time management module is as follows: When executing the creation time request message event, the time request message is packaged according to a custom data packet structure and a sequence number tag is added according to the order of the data packets; the execution time of the send time request message event is calculated based on the actual time of creating the time request message according to the ARINC664 data packet format, the actual time of the time request message being queued in the sending queue for sending, and the multicast send time request message events are recursively added to the event queue. When executing the send time request message event, the time management module fills in the send request timestamp T1 in the send timestamp field of the time request message data packet, sends the time request message data packet to the A and B channels of the data transmission path module, calculates the execution time of the receive time request message event based on the actual network transmission delay and the message receiving clock error of the time agent, and adds the receive time request message event to the event queue. When executing the receive time response message event, the time management module receives time response messages from multiple time agent modules from channels A and B of the data transmission path module, respectively. It uses the send request timestamp T1 and receive request timestamp T2 stored in the data packet content of the first arriving time response message data packet, and the send response timestamp T3 and receive response timestamp T4 in the header of the time response message data packet. The workflow of the time proxy module is as follows: When executing the receive time request message event, the time agent module receives the time request message transmitted from the A and B channels of the data transmission path module, and collects the sending request timestamp T1 and receiving request timestamp T2 of the time request message; When executing the creation time response message event, the time response message is packaged according to a custom data packet structure, and a sequence number tag is added according to the order of the data packets. The time response message is then added to the data packet sending queue of the time agent module. The execution time of the send time response message event is calculated based on the actual time of creating the time response message according to the ARINC data packet format and the actual time of the time response message waiting to be sent in the sending queue. The send time response message event is then added to the event queue. When executing the send time response message event, the time agent module fills in the send response timestamp T3 in the send timestamp field of the time response message data packet, sends the time response message data packet to the A and B channels of the data transmission path module, calculates the execution time of the receive time response message event based on the network transmission delay and the message reception clock error of the time management terminal, and adds the receive time response message event to the event queue.
2. The discrete event simulation method for ARINC664 time management function according to claim 1, characterized in that... The time management module and the time agent module package the time request message and the time response message according to the data package defined below: The member variables of the data packet header are as follows: 1) Message types: including time request messages and time response messages; 2) Channel, indicating whether the message comes from channel A or channel B; 3) The sending end: Which system did the message originate from? 4) Sending timestamp: The sending system time when the message is sent at the application layer; 5) The receiving end: to which end system is the message sent to? 6) Receive timestamp: The system time of the receiving end when the application layer receives the message; 7) Serial number, confirming the order of message confirmation data packets, ensuring the integrity of data transmission order; 8) The data packet size is the sum of the header size and the content size, and must comply with the ARINC664 limit on data packet size; The data packet content carries corresponding data according to the message type. The time request message carries the sending request timestamp T1 and the sequence number of the request / response message, while the time response message carries the sending request timestamp T1 and the receiving request timestamp T2 of the response time request message.
3. The discrete event simulation method for ARINC664 time management function according to claim 2, characterized in that... The message type also includes a timestamp list message, which carries the sending request timestamp T1 and receiving request timestamp T2 of the time request message, and the sending response timestamp T3 and receiving response timestamp T4 of the time response message for the response time request message.
4. The discrete event simulation method for ARINC664 time management function according to claim 1, characterized in that... In each time management cycle, regardless of whether the corresponding time response message has been received, the time management module will send timestamp list messages to each time agent module in sequence after the agreed time when the time request message is sent.
5. A discrete event simulation method for ARINC664 time management function according to claim 1, characterized in that... The workflow of the data transmission path module is as follows: When executing the transmission time request message event, record the timestamp when the time request message data packet arrives at the transmission path, and wait for a fixed transmission delay on the A / B channel transmission path according to the data packet channel setting. After adding the clock error, it is passed to the time agent module. When executing the transmission time response message event, the timestamp of when the time response message data packet arrives at the transmission path is recorded, and the packet waits for a fixed transmission delay on the A / B channel transmission path according to the data packet channel setting. After adding the clock error, the packet is then transmitted to the time management module.
6. A discrete event simulation method for ARINC664 time management function according to claim 1, characterized in that... The data recorded in the statistics management module is as follows: 1) Perform a round of time management function, and compile a list of timestamps of data transmission recorded by the time management module, the current actual time source, and the time source of the management terminal; 2) Perform a round of time management function, and count the current actual simulation time source and the terminal time source maintained by each time agent module; 3) Count the number of unresponsive channels A and B recorded by the time management module and the time agent module; 4) The time management module and the time agent module record the number of duplicate responses for channel A and the number of duplicate responses for channel B; 5) The statistics time management module records the sender, recipient, and timestamp of dropped data packets; 6) The statistics time management module records the sender, recipient, and timestamp of the erroneous data packets.
Citation Information
Patent Citations
Simulation and demonstration system for design and validation of AFDX (Avionics Full Duplex Switched Ethernet) network and simulation and demonstration method thereof
CN101894192A
Simulation system of simulating switched Ethernet clock synchronization
CN103647682A
