DEENESPTFRRUARHIKOZHNL

命名空间 ara::tsync

用户指南人工智能生成

为同步时基、高精度时间戳和状态监控提供标准化接口。
AI 生成 未审核 模型: gemini-3.8-flash-medium · 推理强度: medium · 温度: 不可控 · 提示词: aa3b87a713ce 来源 未决问题(2)
译自德文指南gemini-3.8-flash-low · 2026-10-13 · 德文原文

为同步时基、高精度时间戳和状态监控提供标准化接口。

命名空间 ara::tsync 通过 SynchronizedTimeBaseConsumer 将应用程序连接到已配置的时基,从而在 Adaptive Platform 上提供用于同步时间访问的接口。时间采集通过基于纳秒级分辨率 [SWS_TS_01251] 的类型 Timestamp 高精度时间戳进行。应用程序通过如 SynchronizationStatus [SWS_TS_01050] 等状态指示器监视同步性。作为一项基本约束条件,异步通知回调被设计为非线程安全,并且必须处理与时间守护进程(Time-Daemon)的连接丢失。

上下文

命名空间 ara::tsync 在 AUTOSAR Adaptive Platform 内提供用于高精度时间同步的接口。它允许应用程序读取同步的时间点、监视同步状态以及记录测量值以供验证使用。对于消费端应用程序而言,核心角色由类 SynchronizedTimeBaseConsumer 承担,该类封装了对通过 InstanceSpecifier 配置的时基的访问。在提供方,SynchronizedTimeBaseProvider 作为提供和控制时基的访问点。

时间表示的基础是伪时钟 TimeBase,通过它将类型别名 Timestamp 定义为 std::chrono::time_point<TimeBase, std::chrono::nanoseconds> [SWS_TS_01251]。实际的同步工作以及与诸如 IEEE 802.1AS 或 PTP 等总线协议的连接通常通过后台服务进行。Interpretation:该时间守护进程与 ara::tsync 的实例进行跨进程通信,这可以通过特定错误 TsyncErrc::kDaemonConnectionLost [SWS_TS_00901] 得到证实。 问题 Q-dd9d1a36f7573a03 (未决)该架构还辅以如 ConsumerTimeBaseValidationNotification 和 ProviderTimeBaseValidationNotification 等接口,以及用于运行时间和精度测量的各种数据结构(例如 TimeMasterMeasurementType、TimeSlaveMeasurementType、PdelayInitiatorMeasurementType 和 PdelayResponderMeasurementType)。

diag_tsync_context ConsumerApp Consumer-Anwendung Consumer SynchronizedTimeBaseConsumer ConsumerApp->Consumer 使用 ProviderApp Provider- / Validator-Anwendung Provider SynchronizedTimeBaseProvider ProviderApp->Provider 使用 TimeBase TimeBase (std::chrono Pseudo-Uhr) Consumer->TimeBase referenziert Daemon Time Sync Daemon Consumer->Daemon IPC / Synchronisation Provider->Daemon IPC / Bereitstellung

上下文图:命名空间 ara::tsync 中应用程序、接口类和时间守护进程之间的交互。来源:[SWS_TS_00901]、[SWS_TS_01251]。

生命周期

同步时基的生命周期由状态结构和离散状态转换决定。时间状态的快照(包括所有元数据)由 SynchronizedTimeBaseStatus 表示。通信和同步状态通过枚举 SynchronizationStatus [SWS_TS_01050] 进行控制:

  • kNotSynchronizedUntilStartup:系统启动后第一次成功同步前的初始状态。
  • kSynchronized:时基与 Time-Master 同步。
  • kSynchToGateway:通过网关进行同步。
  • kTimeOut:在定义的时间窗口内无法建立或保持同步。

除通信状态外,枚举 LeapJump [SWS_TS_01051] 还记录时间基准的跳变校正:kTimeLeapNone 表示无阈值超限的连续运行,而 kTimeLeapFuture 和 kTimeLeapPast 则分别指示向未来或过去的重大校正。

关于并发性需注意,根据规范,SynchronizationNotifier [SWS_TS_14222]、SynchronizedTimeBaseNotifier [SWS_TS_14221] 和 TimePrecisionNotifier [SWS_TS_14223] 等回调类型被归类为非线程安全。因此,状态转换(尤其是发生超时或重新同步时)需要由应用程序端进行同步。

diag_sync_status init kNotSynchronizedUntilStartup kNotSynchronizedUntilStartup (Initialzustand) init->kNotSynchronizedUntilStartup kSynchronized kSynchronized (Time Master) kNotSynchronizedUntilStartup->kSynchronized 与 Master 同步 kSynchToGateway kSynchToGateway (Gateway) kNotSynchronizedUntilStartup->kSynchToGateway 与网关同步 kTimeOut kTimeOut (Timeout) kNotSynchronizedUntilStartup->kTimeOut Zeitfenster abgelaufen kSynchronized->kTimeOut Sync-Verlust kSynchToGateway->kTimeOut Sync-Verlust kTimeOut->kSynchronized Re-Synchronisation kTimeOut->kSynchToGateway Re-Synchronisation

状态图:同步时间基准的生命周期与通信状态。来源:[SWS_TS_01050]。

使用路径

消费者应用程序使用同步时间基准的典型流程分为以下步骤:

  1. 初始化与绑定:应用程序为所需的时间基准实例化 SynchronizedTimeBaseConsumer,并指定匹配的 InstanceSpecifier。
  2. 注册通知:为了监视同步状态,应用程序会传递回调函数。其中包括用于 SynchronizationStatus 更改的 SynchronizationNotifier [SWS_TS_14222]、用于详细状态快照(SynchronizedTimeBaseStatus)的 SynchronizedTimeBaseNotifier [SWS_TS_14221] 以及用于高精度测量数据(TimePrecisionMeasurement)的 TimePrecisionNotifier [SWS_TS_14223]。
  3. 时间戳查询:当处于状态 kSynchronized 或 kSynchToGateway [SWS_TS_01050] 时,应用程序读取类型为 Timestamp [SWS_TS_01251] 的高精度时间值。
  4. 对状态跳变和时间跳变的响应:如果通知指示 LeapJump 不等于 kTimeLeapNone [SWS_TS_01051] 或转换到 kTimeOut [SWS_TS_01050],则应用程序会调整内部定时器或转入降级模式。
  5. 用户数据传输:如果在时间同步过程中传输特定于用户的有效载荷数据,则使用结构体 UserData。

错误场景

该命名空间的错误处理遵循基于错误域 TsyncErrorDomain 的 AUTOSAR 标准模型。通过 GetTsyncErrorDomain() [SWS_TS_00909] 访问该全局域。错误原因由枚举类型 TsyncErrc [SWS_TS_00901] 描述:

  • kDaemonConnectionLost:请求的操作失败,因为与 Time-Sync-Daemon 的连接已断开。
  • kLimitsExceeded:传递或计算的值超出了允许的值范围。
  • kFunctionNotSupported:当前配置或平台环境中不支持所请求的功能。
  • kInvalidUserDataSize:传递的用户数据长度超过了由 UserData::kMaxUserDataSize 定义的当前 3 字节的最大值。

ara::core::ErrorCode 的实例通过辅助函数 MakeErrorCode [SWS_TS_00910] 创建。该函数被声明为 noexcept 且是线程安全的。对于基于异常的架构,该命名空间提供了异常类 TsyncException。

本指南基于针对模块 tsync 的 AUTOSAR Adaptive Platform R25-11 规范。

主题图

KI-gestützte Gruppierung auf Basis der Records und Spezifikationsauszüge; keine Gliederung aus der AUTOSAR-Spezifikation.

类图

Abgerundete Rahmen = Namespace- bzw. Klassen-Scopes; hohle Dreieckspfeile = Vererbung (zeigt zur Basisklasse); graue Boxen = namespace-fremde bzw. externe Basisklassen. Klicken öffnet die jeweilige Klassen- bzw. cppreference-Seite.

G cluster_ns ara::tsync nara__tsync__ConsumerTimeBaseValidationNotification ConsumerTimeBaseValidationNotification nara__tsync__PdelayInitiatorMeasurementType «struct» PdelayInitiatorMeasurementType nara__tsync__PdelayResponderMeasurementType «struct» PdelayResponderMeasurementType nara__tsync__ProviderTimeBaseValidationNotification ProviderTimeBaseValidationNotification nara__tsync__SynchronizedTimeBaseConsumer SynchronizedTimeBaseConsumer nara__tsync__SynchronizedTimeBaseProvider SynchronizedTimeBaseProvider nara__tsync__SynchronizedTimeBaseStatus SynchronizedTimeBaseStatus nara__tsync__TimeBase «struct» TimeBase nara__tsync__TimeMasterMeasurementType «struct» TimeMasterMeasurementType nara__tsync__TimePrecisionMeasurement «struct» TimePrecisionMeasurement nara__tsync__TimeSlaveMeasurementType «struct» TimeSlaveMeasurementType nara__tsync__TsyncErrorDomain TsyncErrorDomain next_ara__core__ErrorDomain ara::core::ErrorDomain nara__tsync__TsyncErrorDomain->next_ara__core__ErrorDomain nara__tsync__TsyncException TsyncException next_ara__core__Exception ara::core::Exception nara__tsync__TsyncException->next_ara__core__Exception nara__tsync__UserData «struct» UserData

详细视图

请在大纲中选择一个条目。

Zeitbasen

Class SynchronizedTimeBaseConsumer is the access to the synchronized timebase referenced by the InstanceSpecifier

Class SynchronizedTimeBaseProvider is the access to the synchronized timebase referenced by the IntstanceSpecifier

This class represents a snapshot of a time point including his states

The class TimeBase is a pseudo-clock

Structure to define user data

Timestamp 类型别名

Standard timestamp type as alias of a generic time_point .

Synchronisationsstatus

LeapJump 枚举

Enumeration that is used to express the leap jump of a time base. .

enum class LeapJump : std::uint32_t {...};

Enumeration that is used to express the communication state of a time base. .

enum class SynchronizationStatus : std::uint32_t {...};

Statusmeldungen

Callback interface to notify Consumer Application about the availability of a new data block recorded for the Time Base

Callback interface to notify (Validator) Application about the availability of a new data block recorded for the Time Base

Notifier function .

using SynchronizationNotifier = std::function<void(const SynchronizationStatus&)>;

Notifier function .

using SynchronizedTimeBaseNotifier = std::function<void(const SynchronizedTimeBaseStatus&)>;

Notifier function .

using TimePrecisionNotifier = std::function<void(const TimePrecision Measurement&)>;

Zeitmessung

Structure with detailed timing data for the pDelay Initiator .

Structure with detailed timing data for the pDelay Responder .

Structure with detailed data for validation of the Time Master .

Structure with detailed data for precision measurement of the Time Slave .

Structure with detailed data for validation of the Time Slave .

Fehlerbehandlung

Defines a class representing the Time Synchronization error domain.

继承自 ara::core::ErrorDomain

Defines a class for exceptions to be thrown by the Time Synchronization.

继承自 ara::core::Exception

Returns a reference to the global TsyncErrorDomain object.

const ara::core::ErrorDomain & GetTsyncErrorDomain () noexcept;

Creates an instance of ErrorCode.

TsyncErrc 枚举

Defines an enumeration class for the Time Synchronization error codes.

enum class TsyncErrc : ara::core::ErrorDomain::CodeType {...};

枚举

枚举 LeapJump [SWS_TS_01051] Upstream: RS_TS_00009 原文尚未导入

enum class LeapJump :          std::uint32_t {...};

Enumeration that is used to express the leap jump of a time base. .

Header-Datei#include "ara/tsync/synchronized_time_base_status.h"
Forwarding-Header#include "ara/tsync/tsync_fwd.h"
Scopenamespace ara::tsync
SymbolLeapJump
Basistypstd::uint32_t

Werte

EnumeratorBeschreibung
kTimeLeapNone=0 No adjustment back or greater than a certain threshold has been made.
kTimeLeapFuture=1 An adjustment greater than a certain threshold has been made.
kTimeLeapPast=2 An adjustment back in time greater than a certain threshold has been made.

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

Record
AUTOSAR/AP/record/SWS_TS_01051
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_01051@rel:R25-11#850089b1
Content hash
850089b1
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_01051
Status: valid/unmigrated Version: rel:R25-11#d1e183ad Versionshistorie & Revisions (1 transition, 7 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_01051@rel:R25-11#d1e183ad
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#0f3ec5532026-09-30
  • R20-11rel:R20-11#5e4e15cc2026-10-14
  • R21-11rel:R21-11#5e4e15cc2026-10-14
  • R22-11rel:R22-11#5e4e15cc2026-10-14
  • R23-11rel:R23-11#8dcaedd02026-10-14
  • R24-11rel:R24-11#8dcaedd02026-10-14
  • R25-11rel:R25-11#d1e183ad2026-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

枚举 SynchronizationStatus [SWS_TS_01050] Upstream: RS_TS_00009 原文尚未导入

enum class SynchronizationStatus :               std::uint32_t {...};

Enumeration that is used to express the communication state of a time base. .

Header-Datei#include "ara/tsync/synchronized_time_base_status.h"
Forwarding-Header#include "ara/tsync/tsync_fwd.h"
Scopenamespace ara::tsync
SymbolSynchronizationStatus
Basistypstd::uint32_t

Werte

EnumeratorBeschreibung
kNotSynchronizedUntilStartup=0 The TB is not synchronized until startup (inital state)
kTimeOut= 0x1 The TB was not synchronized within a certain time frame.
kSynchronized= 0x2 The TB is in sync with the time master.
kSynchToGateway= 0x3 The TB is in sync with the gateway.
AI 生成 未审核 模型: gemini-3.8-flash-medium · 推理强度: medium · 温度: 不可控 · 提示词: 2b617e90b13f 来源
译自德文指南gemini-3.8-flash-low · 2026-10-13 · 德文原文

枚举 SynchronizationStatus 表示命名空间 ara::tsync 中时间基准的通信和同步状态 [SWS_TS_01050]。该类型基于 std::uint32_t,并通过头文件 ara/tsync/synchronized_time_base_status.h 以及转发头文件 ara/tsync/tsync_fwd.h 提供 [SWS_TS_01050]。该枚举定义了四种状态:

  • kNotSynchronizedUntilStartup (= 0):在系统启动前时间基准未同步(初始状态)[SWS_TS_01050]。
  • kTimeOut (= 0x1):时间基准在给定的时间窗口内未同步 [SWS_TS_01050]。
  • kSynchronized (= 0x2):时间基准与 Time-Master 同步 [SWS_TS_01050]。
  • kSynchToGateway (= 0x3):时间基准与网关同步 [SWS_TS_01050]。

状态的同步获取通过类 ara::tsync::SynchronizedTimeBaseStatus 的方法 GetSynchronizationStatus() 进行,该方法以线程安全和异常安全(noexcept)的方式提供创建状态对象时的状态 [SWS_TS_01053]。对于状态更改时的通知,ara/tsync/synchronized_time_base_consumer.h 中存在类型别名 SynchronizationNotifier(std::function<void(const SynchronizationStatus &)>),其被显式指定为非线程安全 [SWS_TS_14222]。

发生错误或缺少同步时,必须注意关联方法的行为:如果时基从未同步过且状态为 kNotSynchronizedUntilStartup,则方法 GetCreationTime() 返回一个空的 ara::core::Optional,因为在同步时间内不存在有效的创建时间点 [SWS_TS_01055]。

本文本由 AI 系统生成,仅基于 AUTOSAR R25-11 的规范数据。

实现者指南即将推出(复杂度 I1)

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

Record
AUTOSAR/AP/record/SWS_TS_01050
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_01050@rel:R25-11#6f53b84d
Content hash
6f53b84d
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_01050
Status: valid/unmigrated Version: rel:R25-11#f7498bf9 Versionshistorie & Revisions (1 transition, 7 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_01050@rel:R25-11#f7498bf9
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#b39bcd9d2026-09-30
  • R20-11rel:R20-11#7601b2582026-10-14
  • R21-11rel:R21-11#c9689b3f2026-10-14
  • R22-11rel:R22-11#c9689b3f2026-10-14
  • R23-11rel:R23-11#1e604bb62026-10-14
  • R24-11rel:R24-11#5b49085a2026-10-14
  • R25-11rel:R25-11#f7498bf92026-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

枚举 TsyncErrc [SWS_TS_00901] Upstream: RS_AP_00130, RS_AP_00122, RS_AP_00127, RS_AP_00154

enum class TsyncErrc :             ara::core::ErrorDomain::CodeType {...};

Defines an enumeration class for the Time Synchronization error codes.

Header-Datei#include "ara/tsync/tsync_error_domain.h"
Forwarding-Header#include "ara/tsync/tsync_fwd.h"
Scopenamespace ara::tsync
SymbolTsyncErrc
Basistypara::core::ErrorDomain::CodeType

Werte

EnumeratorBeschreibung
kDaemonConnectionLost=1 The action cannot be executed, because the connection to time sync daemon is currently lost.
kLimitsExceeded=2 The value exceeds valid value range
kFunctionNotSupported=3 The requested function is not supported
kInvalidUserDataSize=4 The length of the user data exceeded the maximum allowed size, defined by UserData::kMaxUserDataSize (currently 3 bytes).
AI 生成 未审核 模型: gemini-3.8-flash-medium · 推理强度: medium · 温度: 不可控 · 提示词: bf6ea0154525 来源 未决问题(1)
译自德文指南gemini-3.8-flash-low · 2026-10-13 · 德文原文

枚举 TsyncErrc 定义功能集群 Time Synchronization 的标准化错误代码 [SWS_TS_00901]。它基于 ara::core::ErrorDomain::CodeType 并在命名空间 ara::tsync 内声明;此外还通过 ara::tsync::TsyncErrorDomain::Errc 提供了一个别名 [SWS_TS_01266]。线程安全函数 MakeErrorCode 用于生成完整的错误对象,该函数将 TsyncErrc 值与特定于制造商的附加数据链接为 ara::core::ErrorCode [SWS_TS_00910]。

该规范定义了四个具体的错误值 [SWS_TS_00901]:

  • kDaemonConnectionLost (=1):无法执行该操作,因为与 Time-Sync-Daemon 的连接已中断。
  • kLimitsExceeded (=2):传入的参数超出了允许的值范围。例如当请求的速率校正无效时,这会在 SetRateCorrection 中发生 [SWS_TS_01110]。
  • kFunctionNotSupported (=3):不支持请求的功能。解释:这大概涉及可选硬件或接口功能不可用的实现。 问题 Q-e22067d84fd6adb4 (未决)
  • kInvalidUserDataSize (=4):有效载荷的长度超过了由 UserData::kMaxUserDataSize 指定的 3 字节最大大小。该错误发生于 SetTime [SWS_TS_01107] 以及 SetUserData [SWS_TS_01112]。

类 ara::tsync::SynchronizedTimeBaseProvider 中用于时间和数据更新的方法(如 SetTime、UpdateTime、SetRateCorrection 和 SetUserData)通过 ara::core::Result<void> 同步返回结果,并被指定为非线程安全 [SWS_TS_01107] [SWS_TS_01108] [SWS_TS_01110] [SWS_TS_01112]。根据规范,在出错时不会应用回滚语义(no_rollback_semantics)[SWS_TS_01107] [SWS_TS_01110] [SWS_TS_01112]。

本段文本由 AI 生成,基于 R25-11 规范版本。

实现者指南即将推出(复杂度 I1)

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

Record
AUTOSAR/AP/record/SWS_TS_00901
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_00901@rel:R25-11#959eccd5
Content hash
959eccd5
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_00901
Status: valid/unmigrated Version: rel:R25-11#9d3829f4 Versionshistorie & Revisions (1 transition, 4 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_00901@rel:R25-11#9d3829f4
Point-in-Time History:
Recorded Revisions (4):
  • R25-11rel:R25-11#e7de222a2026-09-30
  • R23-11rel:R23-11#7a766fcd2026-10-14
  • R24-11rel:R24-11#4086ebd92026-10-14
  • R25-11rel:R25-11#9d3829f42026-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

类型别名

类型别名 SynchronizationNotifier [SWS_TS_14222] Upstream: RS_TS_00034 原文尚未导入

using SynchronizationNotifier = std::function<void(const SynchronizationStatus&)>;

Notifier function .

Header-Datei#include "ara/tsync/synchronized_time_base_consumer.h"
Scopenamespace ara::tsync
SymbolSynchronizationNotifier
Thread-Sicherheitnot thread-safe

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

Record
AUTOSAR/AP/record/SWS_TS_14222
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_14222@rel:R25-11#591c24eb
Content hash
591c24eb
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_14222
Status: valid/unmigrated Version: rel:R25-11#cf8d66fe Versionshistorie & Revisions (1 transition)
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_14222@rel:R25-11#cf8d66fe
Point-in-Time History:
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

类型别名 SynchronizedTimeBaseNotifier [SWS_TS_14221] Upstream: RS_TS_00034 原文尚未导入

using SynchronizedTimeBaseNotifier = std::function<void(const SynchronizedTimeBaseStatus&)>;

Notifier function .

Header-Datei#include "ara/tsync/synchronized_time_base_consumer.h"
Scopenamespace ara::tsync
SymbolSynchronizedTimeBaseNotifier
Thread-Sicherheitnot thread-safe

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

Record
AUTOSAR/AP/record/SWS_TS_14221
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_14221@rel:R25-11#9abbeb6b
Content hash
9abbeb6b
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_14221
Status: valid/unmigrated Version: rel:R25-11#e5ecbd11 Versionshistorie & Revisions (1 transition)
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_14221@rel:R25-11#e5ecbd11
Point-in-Time History:
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

类型别名 TimePrecisionNotifier [SWS_TS_14223] Upstream: RS_TS_00034 原文尚未导入

using TimePrecisionNotifier = std::function<void(const TimePrecision Measurement&)>;

Notifier function .

Header-Datei#include "ara/tsync/synchronized_time_base_consumer.h"
Scopenamespace ara::tsync
SymbolTimePrecisionNotifier
Thread-Sicherheitnot thread-safe

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

Record
AUTOSAR/AP/record/SWS_TS_14223
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_14223@rel:R25-11#82d74418
Content hash
82d74418
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_14223
Status: valid/unmigrated Version: rel:R25-11#080bdbbd Versionshistorie & Revisions (1 transition)
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_14223@rel:R25-11#080bdbbd
Point-in-Time History:
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

类型别名 Timestamp [SWS_TS_01251] Upstream: RS_AP_00130, RS_TS_00005 原文尚未导入

using Timestamp = std::chrono::time_point<TimeBase, std::chrono::nanoseconds>;

Standard timestamp type as alias of a generic time_point .

Header-Datei#include "ara/tsync/timestamp.h"
Scopenamespace ara::tsync
SymbolTimestamp

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

Record
AUTOSAR/AP/record/SWS_TS_01251
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_01251@rel:R25-11#e74d025f
Content hash
e74d025f
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_01251
Status: valid/unmigrated Version: rel:R25-11#c65db4b9 Versionshistorie & Revisions (1 transition, 7 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_01251@rel:R25-11#c65db4b9
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#106ad11b2026-09-30
  • R20-11rel:R20-11#1c46dc512026-10-14
  • R21-11rel:R21-11#1c46dc512026-10-14
  • R22-11rel:R22-11#0b7701762026-10-14
  • R23-11rel:R23-11#c65db4b92026-10-14
  • R24-11rel:R24-11#c65db4b92026-10-14
  • R25-11rel:R25-11#c65db4b92026-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

自由函数文档

函数 GetTsyncErrorDomain [SWS_TS_00909] Upstream: RS_AP_00120, RS_AP_00130, RS_AP_00154

const ara::core::ErrorDomain & GetTsyncErrorDomain () noexcept;

Returns a reference to the global TsyncErrorDomain object.

AI 生成 未审核 模型: gemini-3.8-flash-medium · 推理强度: medium · 温度: 不可控 · 提示词: 3848538f31e7 来源 未决问题(1)
译自德文指南gemini-3.8-flash-low · 2026-10-13 · 德文原文

使用

同步函数 GetTsyncErrorDomain 属于命名空间 ara::tsync,并通过头文件 ara/tsync/tsync_error_domain.h 包含 [SWS_TS_00909]。该调用无参数,用于获取对时间同步全局 TsyncErrorDomain 对象的引用 [SWS_TS_00909]。

作为返回值,该函数提供对该类型为 const ara::core::ErrorDomain & 的全局错误域对象的常量引用 [SWS_TS_00909]。解读:所提供的实例在 AUTOSAR Adaptive 的错误处理概念中可用作参考基准,以识别、归类时间同步领域的模块特定错误码,或将其与其他错误域进行比较。 问题 Q-cf1fce412576bca3 (未决)

错误处理与异常安全性

函数签名显式声明为 noexcept 并指定为异常安全(exception safe)[SWS_TS_00909]。这意味着在执行期间不会抛出异常。由于该函数仅返回对已存在的全局域对象的引用,因此不会发生内部错误状态,并且针对该调用既不存在特定错误码,也不存在错误消息 [SWS_TS_00909]。

并发性与限制

根据规范,GetTsyncErrorDomain 被归类为线程安全(thread-safe)[SWS_TS_00909]。因此,可以从不同线程并行执行调用,而无需事先进行同步或锁定机制。根据规范,该调用不存在特殊的顺序条件或前置条件 [SWS_TS_00909]。

该文本由人工智能基于 AUTOSAR 规范生成。

Header-Datei#include "ara/tsync/tsync_error_domain.h"
Scopenamespace ara::tsync
Exception-Sicherheitexception safe
Thread-Sicherheitthread-safe

Rückgabewert

TypBeschreibung
const ara::core::ErrorDomain &Return a reference to the global TsyncErrorDomain object.

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

Record
AUTOSAR/AP/record/SWS_TS_00909
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_00909@rel:R25-11#95ef1e93
Content hash
95ef1e93
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_00909
Status: valid/unmigrated Version: rel:R25-11#a57021f4 Versionshistorie & Revisions (1 transition, 4 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_00909@rel:R25-11#a57021f4
Point-in-Time History:
Recorded Revisions (4):
  • R25-11rel:R25-11#9607cbbd2026-09-30
  • R23-11rel:R23-11#cff138772026-10-14
  • R24-11rel:R24-11#ea375f2a2026-10-14
  • R25-11rel:R25-11#a57021f42026-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

函数 MakeErrorCode [SWS_TS_00910] Upstream: RS_AP_00120, RS_AP_00121, RS_AP_00130, RS_AP_00154

ara::core::ErrorCode MakeErrorCode (ara::tsync::TsyncErrc code, ara::core::ErrorDomain::SupportDataType data) noexcept;

Creates an instance of ErrorCode.

AI 生成 未审核 模型: gemini-3.8-flash-medium · 推理强度: medium · 温度: 不可控 · 提示词: ad8052caa2c8 来源
译自德文指南gemini-3.8-flash-low · 2026-10-13 · 德文原文

函数MakeErrorCode用于为命名空间ara::tsync中时间同步的错误域同步创建ara::core::ErrorCode对象[SWS_TS_00910]。它通过头文件ara/tsync/tsync_error_domain.h提供,并将时间同步的错误编号转换为 AUTOSAR Adaptive 的标准化错误处理模型。

参数与返回值

  • code(ara::tsync::TsyncErrc):标识域[SWS_TS_00910]的特定错误编号。
  • data(ara::core::ErrorDomain::SupportDataType):传递所发生错误的供应商特定附加数据[SWS_TS_00910]。
  • 返回值:返回一个已初始化的ara::core::ErrorCode对象[SWS_TS_00910]。

并发性与执行安全性

该函数使用noexcept声明,并归类为异常安全[SWS_TS_00910];它在运行时不抛出任何异常。此外,该实现被指定为thread-safe [SWS_TS_00910],因此无需额外的同步措施即可从多个线程中并行调用。

相互作用

作为对该基本函数的补充,相关要求[SWS_TS_14213]为命名空间apext::tsync(头文件apext/tsync/fvm_error_domain.h)中的TsyncFvmErrc指定了类似的重载,该重载被定义为constexpr。

本文由 AI 基于 AUTOSAR 规范 R25-11 生成。

实现者指南即将推出(复杂度 I1)

Header-Datei#include "ara/tsync/tsync_error_domain.h"
Scopenamespace ara::tsync
Exception-Sicherheitexception safe
Thread-Sicherheitthread-safe

Parameter (in)

ParameterBeschreibung
codeError code number.
dataVendor defined data associated with the error.

Rückgabewert

TypBeschreibung
ara::core::ErrorCodeAn ErrorCode object.

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

Record
AUTOSAR/AP/record/SWS_TS_00910
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_00910@rel:R25-11#a1ea8d3f
Content hash
a1ea8d3f
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_00910
Status: valid/unmigrated Version: rel:R25-11#2ab21bd3 Versionshistorie & Revisions (1 transition, 4 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_00910@rel:R25-11#2ab21bd3
Point-in-Time History:
Recorded Revisions (4):
  • R25-11rel:R25-11#11d4fda32026-09-30
  • R23-11rel:R23-11#ae1573d92026-10-14
  • R24-11rel:R24-11#1427f2f12026-10-14
  • R25-11rel:R25-11#2ab21bd32026-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