DEENESPTFRRUARHIKOZHNL

struct ara::tsync::TimeMasterMeasurementType

[SWS_TS_00414] Upstream: RS_TS_00034 wording not yet imported

struct TimeMasterMeasurementType final {...};

Structure with detailed data for validation of the Time Master .

Header-Datei#include "ara/tsync/time_validation_measurement_types.h"
Forwarding-Header#include "ara/tsync/tsync_fwd.h"
Scopenamespace ara::tsync

User GuideAI-GENERATED

Serves to record egress timestamps and frame sequences for validating a time master in the network.
AI-GENERATED unreviewed Model: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 2ead85402aa5 Provenance Open questions (3)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original

Serves to record egress timestamps and frame sequences for validating a time master in the network.

The data structure serves to consolidate detailed measurement data for measurement-based validation and runtime monitoring of the time master. For each transmitted synchronization frame, it bundles the transmission timestamp in the global time base via preciseOriginTimestamp [SWS_TS_14140], the network-related egress timestamp syncEgressTimestamp, and the Ethernet frame identifier sequenceId [SWS_TS_14142]. These aggregated measurement values enable downstream analysis instances to perform seamless plausibility checks on jitter and packet sequences. Since the type is declared as a final data container without internal synchronization, concurrent exchange presumably requires additional protection by the caller. Question (open)

Context

The structure ara::tsync::TimeMasterMeasurementType is part of the time validation in module tsync of the AUTOSAR Adaptive Platform. According to the specification, it bundles detailed measurement data for validating a time master. In distributed systems, the time master provides the time reference for connected network nodes. To ensure compliance with required synchronization accuracies and to detect timing deviations during ongoing operation, measurement metrics are recorded directly at the interfaces of the time master.

The definition of the type is provided in the header file ara/tsync/time_validation_measurement_types.h [SWS_TS_14140]. As a central data transfer object, the structure consolidates three elementary measured quantities that arise when sending synchronization messages (sync frames) via Ethernet:

  • preciseOriginTimestamp: The egress timestamp of the sync frame referenced to the global time base in the format ara::tsync::Timestamp [SWS_TS_14140].
  • syncEgressTimestamp: The network-level egress timestamp of the sync frame as a 64-bit integer (std::uint64_t) [SWS_TS_14141].
  • sequenceId: The sequence identifier of the transmitted Ethernet frame as a 16-bit value (std::uint16_t) [SWS_TS_14142].

The structure thus acts as a standardized interface between the actual synchronization service of the time master and downstream monitoring or validation components.

Lifecycle

It is declared as struct TimeMasterMeasurementType final, designating the class as a final data structure with pure value semantics. Because it does not manage dynamic resources and has no inheritance hierarchy, its creation is lightweight. Typically, an instance is created by the time master immediately after transmitting a sync frame, as soon as the physical egress timestamp and the sequence number are available.

The lifetime of an instance is tightly coupled to the evaluation cycle. The data is likely to be passed to the consuming validation instance as a copy or via move operations and discarded after completion of the plausibility check. Question Q-c09487031c2b5638 (open) The structure does not contain any internal synchronization mechanisms such as mutexes. If an instance is exchanged across thread boundaries in concurrent software architectures, responsibility for thread-safe access presumably lies entirely with the caller.

Usage Path

The typical sequence of usage includes determining the measurement values during frame transmission, encapsulation in the structure, and forwarding for validation:

  1. Transmission of the sync frame: The time master transmits a synchronization frame over the Ethernet network, with the frame identifier being recorded in sequenceId [SWS_TS_14142].
  2. Measurement value acquisition: The hardware- or driver-level egress timestamp is acquired as syncEgressTimestamp [SWS_TS_14141]. At the same time, the corresponding global time value is determined and stored as preciseOriginTimestamp [SWS_TS_14140].
  3. Populating the structure: The recorded values are aggregated in an instance of TimeMasterMeasurementType.
  4. Evaluation: The structure is handed over to the validation subsystem, which detects packet losses based on the sequence number and calculates jitter or transmission drifts by comparing the timestamps.
Sequence of measurement data acquisition and validation for the Time MasterTimeMasterMessdatenstrukturTimeValidationCreation and assignment (preciseOriginTimestamp, syncEgressTimestamp, sequenceId)Bereitstellung von TimeMasterMeasurementTypePlausibility check of timestamps and sequence fidelityValidierungsergebnis / Status

Sequence diagram: Typical sequence of acquisition and forwarding of TimeMasterMeasurementType. Sources: [SWS_TS_14140], [SWS_TS_14141], [SWS_TS_14142].

Interpretation: By jointly acquiring the local egress timestamp [SWS_TS_14141] and the global reference time [SWS_TS_14140], the validation logic can determine whether processing delays have occurred in the protocol stack of the time master. Question Q-7454a019d8b9e764 (open)

This guide is based on the AUTOSAR Adaptive Platform Release R25-11 specification and was created automatically.

Member map

Class diagram

Hohle Dreieckspfeile = Vererbung (zeigt zur Basisklasse); Klicken öffnet die jeweilige Klassenseite.

G nara__tsync__TimeMasterMeasurementType777 «struct» TimeMasterMeasurementType + preciseOriginTimestamp + sequenceId + syncEgressTimestamp

Detail view

Select an entry in the outline.

Constants

egress timestamp of Sync frame in Global Time

ara::tsync::Timestamp preciseOriginTimestamp;
sequenceId variable

sequence Id of sent Ethernet frame

std::uint16_t sequenceId;

egress timestamp of Sync frame

std::uint64_t syncEgressTimestamp;

Documentation of constants / variables

variable preciseOriginTimestamp [SWS_TS_14140] Upstream: RS_TS_00034 wording not yet imported

ara::tsync::Timestamp preciseOriginTimestamp;

egress timestamp of Sync frame in Global Time

Header-Datei#include "ara/tsync/time_validation_measurement_types.h"
Scopestruct ara::tsync::TimeMasterMeasurementType
SymbolpreciseOriginTimestamp
Typara::tsync::Timestamp

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_TS_14140
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_14140@rel:R25-11#f10cc5ac
Content hash
f10cc5ac
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_14140
Status: valid/unmigrated Version: rel:R25-11#6002ae8e Versionshistorie & Revisions (1 transition, 8 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_TS_14140@rel:R25-11#6002ae8e
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#f10cc5ac2026-09-30
  • R19-11rel:R19-11#93e923d22026-10-14
  • R20-11rel:R20-11#ce0b905d2026-10-14
  • R21-11rel:R21-11#ce0b905d2026-10-14
  • R22-11rel:R22-11#41c0fa062026-10-14
  • R23-11rel:R23-11#6002ae8e2026-10-14
  • R24-11rel:R24-11#6002ae8e2026-10-14
  • R25-11rel:R25-11#6002ae8e2026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

variable sequenceId [SWS_TS_14142] Upstream: RS_TS_00034 wording not yet imported

std::uint16_t sequenceId;

sequence Id of sent Ethernet frame

Header-Datei#include "ara/tsync/time_validation_measurement_types.h"
Scopestruct ara::tsync::TimeMasterMeasurementType
SymbolsequenceId
Typstd::uint16_t

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_TS_14142
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_14142@rel:R25-11#cd26e2ee
Content hash
cd26e2ee
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_14142
Status: valid/unmigrated Version: rel:R25-11#6981c39b Versionshistorie & Revisions (1 transition, 8 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_TS_14142@rel:R25-11#6981c39b
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#cd26e2ee2026-09-30
  • R19-11rel:R19-11#b5b8102f2026-10-14
  • R20-11rel:R20-11#78bfab7c2026-10-14
  • R21-11rel:R21-11#b86ac6202026-10-14
  • R22-11rel:R22-11#6ccb24eb2026-10-14
  • R23-11rel:R23-11#6981c39b2026-10-14
  • R24-11rel:R24-11#6981c39b2026-10-14
  • R25-11rel:R25-11#6981c39b2026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

variable syncEgressTimestamp [SWS_TS_14141] Upstream: RS_TS_00034 wording not yet imported

std::uint64_t syncEgressTimestamp;

egress timestamp of Sync frame

Header-Datei#include "ara/tsync/time_validation_measurement_types.h"
Scopestruct ara::tsync::TimeMasterMeasurementType
SymbolsyncEgressTimestamp
Typstd::uint64_t

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_TS_14141
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_14141@rel:R25-11#737d705a
Content hash
737d705a
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_14141
Status: valid/unmigrated Version: rel:R25-11#9f2c420d Versionshistorie & Revisions (1 transition, 8 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_TS_14141@rel:R25-11#9f2c420d
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#737d705a2026-09-30
  • R19-11rel:R19-11#d14b42b02026-10-14
  • R20-11rel:R20-11#73a283f02026-10-14
  • R21-11rel:R21-11#73a283f02026-10-14
  • R22-11rel:R22-11#a5706d0f2026-10-14
  • R23-11rel:R23-11#9f2c420d2026-10-14
  • R24-11rel:R24-11#9f2c420d2026-10-14
  • R25-11rel:R25-11#9f2c420d2026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill