Time Daemon Component Requirements#
Time Daemon Requirements
|
status: valid
security: NO
safety: ASIL_B
|
||||
Functional Requirements#
Initialization and Lifecycle#
Component Initialization
|
status: valid
security: NO
safety: ASIL_B
|
||||
On startup the time_daemon component shall apply its configuration and become ready to receive time synchronization data from the time_slave component and to provide time data to the time component (Time (comp__time)). |
|||||
Startup Timeout
|
status: valid
security: NO
safety: ASIL_B
|
||||
If the time_daemon component does not complete its startup within 20 seconds, it shall not provide time data to the time component (Time (comp__time)) and shall not retry the startup. |
|||||
Component Shutdown
|
status: valid
security: NO
safety: ASIL_B
|
||||
On receiving a stop signal (e.g. SIGINT or SIGTERM) the time_daemon component shall stop providing time data and release IPC resources. |
|||||
Start Order Independence
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall not require the time_slave component to be started before it. If the time_slave component is not yet available on startup, the time_daemon component shall continue its own startup and retry establishing the time synchronization channel with the time_slave component until it succeeds or the startup timeout expires. |
|||||
Data Reception and Validation#
Time Synchronization Data Reception
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall receive the time synchronization data provided by the time_slave component. |
|||||
Verification Pipeline#
Synchronization Status Validation
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall validate synchronization status based on received time synchronization data. |
|||||
Synchronization State Stabilization
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall not report time jumps during the configured time span (default: 5 seconds) after initial synchronization to avoid spuriously detected time jumps during startup. |
|||||
Time Jump Detection
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall detect time jumps when the master clock timestamp of a gPTP time sync data update differs from the expected value by more than the configured time span (default: 500 microseconds). Both forward and backward time jumps shall be detected. |
|||||
Timeout Detection
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall detect timeout condition when no new time synchronization data is received within the configured time span (default: 3.3 seconds). |
|||||
Data Provision#
Time Data Provision
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall provide the verified time data to the time component (Time (comp__time)). |
|||||
Provided Time Data Content
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall include in the time data provided to the time component (Time (comp__time), see Time Data Provision (comp_req__time_daemon__time_data_publishing)): the timestamp of the master clock, the corresponding timestamp of the local reference clock, the rate deviation between those two clocks, synchronization status, time jump status, and timeout status. |
|||||
Provided Raw gPTP Data
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall include in the time data provided to the time component (Time (comp__time), see Time Data Provision (comp_req__time_daemon__time_data_publishing)) condensed raw data of the last received Sync/FollowUp pair and the last finished Pdelay measurement. |
|||||
Time Point Qualifier Production
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall provide the synchronization status, time jump status, and timeout status in the time data provided to the time component (Time (comp__time)), such that the time component can derive the time point qualifier (quality indicator) from them. |
|||||
Client Read Access
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall provide functionality for client applications to read the time data. |
|||||
Non-Blocking Read Access
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall provide time data such that reading it does not block the reading thread of a client application indefinitely. |
|||||
Multi-Client Support
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall allow parallel reads of the provided time data from multiple client applications on different CPU cores. |
|||||
Error Handling and Recovery#
Error Reporting
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall log messages via the score::mw::log interface when initialization fails (error level), IPC access fails (error level), verification stage failures occur (warning level), or time synchronization data reception fails (error level). |
|||||
Error Reaction
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall continue providing time data when a time jump, timeout, or loss of synchronization is detected, with the corresponding status set in the provided time data. |
|||||
Time Jump Recovery
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall clear time jump condition after receiving 2 consecutive valid gPTP frames without time jump. |
|||||
Platform Abstraction#
Platform Support
|
status: valid
security: NO
safety: ASIL_B
|
||||
The time_daemon component shall support Linux and QNX 8.0 operating systems. |
|||||