DEENESPTFRRUARHIKOZHNL

struct ara::tsync::PdelayResponderMeasurementType

[SWS_TS_00417] Upstream: RS_TS_00034 wording not yet imported

struct PdelayResponderMeasurementType final {...};

Structure with detailed timing data for the pDelay Responder .

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

User GuideAI-GENERATED

Bundles timestamps and reference time data of a pDelay responder for time validation.
AI-GENERATED unreviewed Model: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 5eb2c3f093f6 Provenance Open questions (2)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original

Bundles timestamps and reference time data of a pDelay responder for time validation.

The data structure ara::tsync::PdelayResponderMeasurementType serves to bundle detailed time measurement data for the pDelay responder within time synchronization. It captures the arrival point in time of the request requestReceiptTimestamp [SWS_TS_14170] as well as the departure point in time of the response responseOriginTimestamp [SWS_TS_14171] in virtual local time along with the associated sequence number. An included reference global time tuple of virtual local and global time enables downstream systems to precisely convert the measured values into global time coordinates.

Context

The data structure ara::tsync::PdelayResponderMeasurementType is defined in the header ara/tsync/time_validation_measurement_types.h and bundles precise time measurement data for the pDelay responder within the functional cluster of time synchronization (tsync). In the peer-to-peer transit time measurement procedure, the responder responds to transit time requests from neighboring network nodes. In order to be able to trace and validate the transmission delay in terms of time as well as the accuracy of the synchronization at link level, the structure captures the decisive timestamps of a measurement cycle. The unambiguous association with the triggering request message is ensured via the field sequenceId [SWS_TS_14174]. Interpretation: The collected measurement data are likely provided primarily for analysis and validation mechanisms (Time Validation) to monitor deviations and transmission delays in the network. Question Q-8e58febf465a0259 (open)

The captured timestamps comprise the exact arrival point in time of the request message requestReceiptTimestamp [SWS_TS_14170] as well as the departure point in time of the associated response responseOriginTimestamp [SWS_TS_14171]. Both values are represented as timestamps in virtual local time (Virtual Local Time). For uniform classification into the platform-wide time model, the structure additionally contains a reference time tuple: This consists of the local time value referenceLocalTimestamp [SWS_TS_14172] and the corresponding global time value referenceGlobalTimestamp [SWS_TS_14173]. Through this, processing entities can precisely convert the events measured in local virtual time into the global time scale.

Lifecycle

As a final struct declaration (struct ... final), PdelayResponderMeasurementType acts as a pure value object (Plain Old Data) without an internal state machine or dynamic memory management. An instance is typically created immediately after the completion of a pDelay transaction. Interpretation: Population of the structure is likely to take place synchronously in the responder's protocol stack as soon as all hardware and interface timestamps are available after sending the message Pdelay_Resp. Question Q-202e7724b43ceac9 (open)

With regard to ownership, the object is passed by value or via immutable references to downstream diagnostic or time validation routines. Since the structure manages no exclusive resources or pointers, the destruction process is trivial and tied to the scope of the calling context. With respect to concurrency, a fully initialized instance is thread-safe for concurrent read accesses; writing modifications require external synchronization if the instance is reused across threads.

Usage Path

The typical flow for capturing and providing the responder measurement data is divided into the following steps:

  1. Reception of the request: Upon arrival of a Pdelay_Req frame, the responder captures the arrival point in time as requestReceiptTimestamp in virtual local time [SWS_TS_14170] and registers the associated sequence number sequenceId [SWS_TS_14174].
  2. Transmission of the response: The responder transmits the response message Pdelay_Resp. When leaving the interface, the departure point in time is recorded as responseOriginTimestamp, likewise in virtual local time [SWS_TS_14171].
  3. Determination of the reference tuple: To convert the measured values into global time, referenceLocalTimestamp [SWS_TS_14172] and referenceGlobalTimestamp [SWS_TS_14173] are determined from the current state of the local instance of global time.
  4. Handover of the measurement data: The fully populated instance of PdelayResponderMeasurementType is handed over to the validation system, which checks the time differences and synchronization accuracies.
Measurement sequence and data capture at the pDelay responderpDelay-InitiatorpDelay-ResponderMessdatenerfassungPdelay_Req (sequenceId)requestReceiptTimestamp erfassensequenceId registrierenPdelay_RespresponseOriginTimestamp erfassenReferenz-Tupel ermitteln(referenceLocalTimestamp,referenceGlobalTimestamp)Pass PdelayResponderMeasurementType

Sequence diagram: Flow of timestamp capture and measurement data provision at the pDelay responder. Sources: [SWS_TS_14170], [SWS_TS_14171], [SWS_TS_14172], [SWS_TS_14173], [SWS_TS_14174].

This class guide is based on the AUTOSAR Adaptive R25-11 specification for the tsync module and describes the structure of measurement data capture.

Member map

Class diagram

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

G nara__tsync__PdelayResponderMeasurementType5 «struct» PdelayResponderMeasurementType + referenceGlobalTimestamp + referenceLocalTimestamp + requestReceiptTimestamp + responseOriginTimestamp + sequenceId

Detail view

Select an entry in the outline.

Constants

value of the local instance of the Global Time of the reference Global Time Tuple used to convert requestReceiptTimestamp and responseOriginTimestamp into Global Time

ara::tsync::Timestamp referenceGlobalTimestamp;

value of the Virtual Local Time of the reference Global Time Tuple used to convert request ReceiptTimestamp and responseOriginTimestamp into Global Time

std::uint64_t referenceLocalTimestamp;

ingress timestamp of Pdelay_Req converted to Virtual Local Time

std::uint64_t requestReceiptTimestamp;

egress timestamp of Pdelay_Resp converted to Virtual Local Time

std::uint64_t responseOriginTimestamp;
sequenceId variable

sequence Id of received Pdelay_Req frame

std::uint16_t sequenceId;

Documentation of constants / variables

variable referenceGlobalTimestamp [SWS_TS_14173] Upstream: RS_TS_00034 wording not yet imported

ara::tsync::Timestamp referenceGlobalTimestamp;

value of the local instance of the Global Time of the reference Global Time Tuple used to convert requestReceiptTimestamp and responseOriginTimestamp into Global Time

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

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

Record
AUTOSAR/AP/record/SWS_TS_14173
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_14173@rel:R25-11#00b943e5
Content hash
00b943e5
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_14173
Status: valid/unmigrated Version: rel:R25-11#266b2811 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_14173@rel:R25-11#266b2811
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#00b943e52026-09-30
  • R19-11rel:R19-11#f83282162026-10-14
  • R20-11rel:R20-11#a01a02a12026-10-14
  • R21-11rel:R21-11#620277252026-10-14
  • R22-11rel:R22-11#a661ed2f2026-10-14
  • R23-11rel:R23-11#266b28112026-10-14
  • R24-11rel:R24-11#266b28112026-10-14
  • R25-11rel:R25-11#266b28112026-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 referenceLocalTimestamp [SWS_TS_14172] Upstream: RS_TS_00034 wording not yet imported

std::uint64_t referenceLocalTimestamp;

value of the Virtual Local Time of the reference Global Time Tuple used to convert request ReceiptTimestamp and responseOriginTimestamp into Global Time

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

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

Record
AUTOSAR/AP/record/SWS_TS_14172
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_14172@rel:R25-11#64a33ae8
Content hash
64a33ae8
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_14172
Status: valid/unmigrated Version: rel:R25-11#7af85590 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_14172@rel:R25-11#7af85590
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#64a33ae82026-09-30
  • R19-11rel:R19-11#61fab16a2026-10-14
  • R20-11rel:R20-11#eb5de9de2026-10-14
  • R21-11rel:R21-11#eb5de9de2026-10-14
  • R22-11rel:R22-11#f73e98162026-10-14
  • R23-11rel:R23-11#7af855902026-10-14
  • R24-11rel:R24-11#7af855902026-10-14
  • R25-11rel:R25-11#7af855902026-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 requestReceiptTimestamp [SWS_TS_14170] Upstream: RS_TS_00034 wording not yet imported

std::uint64_t requestReceiptTimestamp;

ingress timestamp of Pdelay_Req converted to Virtual Local Time

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

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

Record
AUTOSAR/AP/record/SWS_TS_14170
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_14170@rel:R25-11#ba349572
Content hash
ba349572
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_14170
Status: valid/unmigrated Version: rel:R25-11#fcff2282 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_14170@rel:R25-11#fcff2282
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#ba3495722026-09-30
  • R19-11rel:R19-11#c979eea62026-10-14
  • R20-11rel:R20-11#728a09f82026-10-14
  • R21-11rel:R21-11#728a09f82026-10-14
  • R22-11rel:R22-11#a66b3a702026-10-14
  • R23-11rel:R23-11#fcff22822026-10-14
  • R24-11rel:R24-11#fcff22822026-10-14
  • R25-11rel:R25-11#fcff22822026-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 responseOriginTimestamp [SWS_TS_14171] Upstream: RS_TS_00034 wording not yet imported

std::uint64_t responseOriginTimestamp;

egress timestamp of Pdelay_Resp converted to Virtual Local Time

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

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

Record
AUTOSAR/AP/record/SWS_TS_14171
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_14171@rel:R25-11#5a72a505
Content hash
5a72a505
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_14171
Status: valid/unmigrated Version: rel:R25-11#8d62a751 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_14171@rel:R25-11#8d62a751
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#5a72a5052026-09-30
  • R19-11rel:R19-11#39abbef62026-10-14
  • R20-11rel:R20-11#7889897b2026-10-14
  • R21-11rel:R21-11#7889897b2026-10-14
  • R22-11rel:R22-11#75c224bc2026-10-14
  • R23-11rel:R23-11#8d62a7512026-10-14
  • R24-11rel:R24-11#8d62a7512026-10-14
  • R25-11rel:R25-11#8d62a7512026-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_14174] Upstream: RS_TS_00034 wording not yet imported

std::uint16_t sequenceId;

sequence Id of received Pdelay_Req frame

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

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

Record
AUTOSAR/AP/record/SWS_TS_14174
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_14174@rel:R25-11#1660d678
Content hash
1660d678
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_14174
Status: valid/unmigrated Version: rel:R25-11#b7e1d6f6 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_14174@rel:R25-11#b7e1d6f6
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#1660d6782026-09-30
  • R19-11rel:R19-11#1182a87c2026-10-14
  • R20-11rel:R20-11#b8d2e7722026-10-14
  • R21-11rel:R21-11#b8d2e7722026-10-14
  • R22-11rel:R22-11#a0c122e42026-10-14
  • R23-11rel:R23-11#b7e1d6f62026-10-14
  • R24-11rel:R24-11#b7e1d6f62026-10-14
  • R25-11rel:R25-11#b7e1d6f62026-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