|
Safe API Framework 0.1.0 build 384e6ae
Layered API framework for safety-related applications (ERTMS RBC reference targeting CENELEC EN 50128 SIL 4)
|
One rte_dual_msgchannel_t instance's state. Caller-owned storage (REQ-DUAL-MSGCHANNEL-001); opaque in practice, exposed here (not via RTE_DECLARE_STORAGE) only because its size is already small and fixed - callers must still treat every field as private and only reach it through the functions below. More...
#include <rte_dual_msgchannel.h>
Data Fields | |
| rte_netlink_handle_t | link |
| uint32_t | sender_id |
| uint32_t | expected_peer_id |
| uint32_t | next_sequence |
| uint32_t | expected_sequence |
| bool | resync_on_sequence_error |
One rte_dual_msgchannel_t instance's state. Caller-owned storage (REQ-DUAL-MSGCHANNEL-001); opaque in practice, exposed here (not via RTE_DECLARE_STORAGE) only because its size is already small and fixed - callers must still treat every field as private and only reach it through the functions below.
Definition at line 67 of file rte_dual_msgchannel.h.
| rte_netlink_handle_t rte_dual_msgchannel_t::link |
Caller-opened; NOT closed by rte_dual_msgchannel_close().
Definition at line 69 of file rte_dual_msgchannel.h.
| uint32_t rte_dual_msgchannel_t::sender_id |
This instance's own EN 50159 sender_id, stamped on every outbound frame.
Definition at line 70 of file rte_dual_msgchannel.h.
| uint32_t rte_dual_msgchannel_t::expected_peer_id |
Inbound frames whose sender_id differs are rejected (masquerade defense).
Definition at line 71 of file rte_dual_msgchannel.h.
| uint32_t rte_dual_msgchannel_t::next_sequence |
Next outbound sequence_number.
Definition at line 72 of file rte_dual_msgchannel.h.
| uint32_t rte_dual_msgchannel_t::expected_sequence |
Next expected inbound sequence_number (continuity check).
Definition at line 73 of file rte_dual_msgchannel.h.
| bool rte_dual_msgchannel_t::resync_on_sequence_error |
See rte_dual_msgchannel_config_t::resync_on_sequence_error.
Definition at line 74 of file rte_dual_msgchannel.h.