DEENESPTFRRUARHIKOZHNL

类 <SI-Namespace>::proxy::triggers::<Trigger>

[SWS_CM_00727] Upstream: RS_CM_00103, RS_AP_00114

class <Trigger> final {...};

Service proxy Trigger class, one for each Trigger defined in the ServiceInterface in the role trigger.

Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Forwarding-Header#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy/<SiShortname>_proxy_fwd.h"
Scopenamespace <SI-Namespace>::proxy::triggers

用户指南人工智能生成

订阅无数据的服务触发器,并为客户端应用程序统计传入的触发脉冲。
AI 生成 未审核 模型: gemini-3.8-flash-medium · 推理强度: medium · 温度: 不可控 · 提示词: f0b35174b21c 来源 未决问题(1)
译自德文指南gemini-3.8-flash-low · 2026-10-13 · 德文原文

订阅无数据的服务触发器,并为客户端应用程序统计传入的触发脉冲。

类 <SI-Namespace>::proxy::triggers::<Trigger> 允许客户端应用程序通过 Communication Management 订阅无数据的触发脉冲 [SWS_CM_00723]。通过 SetReceiveHandler() 注册回调后,应用程序使用 GetNewTriggers() 读取新到达的脉冲 [SWS_CM_00226],[SWS_CM_00250]。除 UnsetReceiveHandler() 外,默认保证异常安全性 [SWS_CM_11614]。

上下文

生成的代理类 <SI-Namespace>::proxy::triggers::<Trigger> 在客户端表示恰好一个在服务接口中被建模为角色 trigger 的触发器元素 AUTOSAR_AP_SWS_CommunicationManagement §8 “Service proxy Trigger class”。与基于事件的数据流不同,触发器传输不带有效负载的纯触发脉冲。该类充当使用它的客户端应用程序、Communication Management (ara::com) 以及 E2E 监控系统之间的中介。其核心任务是控制传入触发器的订阅,为脉冲到达或状态更改注册通知回调,并通过计数器提供已到达触发的次数 [SWS_CM_00226],[SWS_CM_00250]。

生命周期

<SI-Namespace>::proxy::triggers::<Trigger> 实例的生命周期绑定到父服务代理对象的生命周期,并在其中作为类成员存在。在状态方面,触发器订阅经历多个阶段,这些阶段由 ara::com::SubscriptionState 映射并可通过 GetSubscriptionState() 查询 [SWS_CM_01105]:

  • 未订阅:调用 Subscribe() 之前或成功 Unsubscribe() 之后的初始状态 [SWS_CM_00723],[SWS_CM_00810]。
  • 订阅挂起(kSubscriptionPending):触发 Subscribe() 之后确认订阅期间的中间状态 [SWS_CM_00723]。
  • 已订阅(kSubscribed):订阅处于活动状态;传入的触发脉冲会递增内部计数器并通知已注册的处理程序 [SWS_CM_00226],[SWS_CM_00250]。

在状态 kSubscribed 或 kSubscriptionPending 下再次调用 Subscribe() 无效并直接返回而不执行任何操作 [SWS_CM_00723]。若在调用时触发器订阅不存在,Unsubscribe() 的行为与此类似 [SWS_CM_00810]。为了观察状态变化,应用程序可以通过 SetSubscriptionStateChangeHandler() 设置相应的回调 [SWS_CM_01107] 或通过 UnsetSubscriptionStateChangeHandler() 注销 [SWS_CM_01108]。

TriggerState kNotSubscribed 未订阅 kSubscriptionPending kSubscriptionPending kNotSubscribed->kSubscriptionPending Subscribe() kSubscriptionPending->kNotSubscribed Unsubscribe() kSubscribed kSubscribed kSubscriptionPending->kSubscribed 确认 kSubscribed->kNotSubscribed Unsubscribe()

状态图:包含通过 Subscribe 和 Unsubscribe 进行转换的触发器订阅生命周期。来源:[SWS_CM_00723]、[SWS_CM_00810]、[SWS_CM_01105]。

使用路径

事件驱动处理触发信号的典型使用路径包括配置回调、激活订阅以及查询计数器:

  1. 处理程序注册:应用程序可选地通过 SetSubscriptionStateChangeHandler() 设置状态处理程序 [SWS_CM_01107],且必须通过 SetReceiveHandler() 设置接收处理程序 [SWS_CM_00250]。对于并发架构,提供了带有专用 ExecutorT 的重载,用于指定异步计算的执行上下文 [SWS_CM_00352],[SWS_CM_01106]。
  2. 请求订阅:使用 Subscribe() 启动触发器订阅 [SWS_CM_00723]。
  3. 信号接收与计数器查询:一旦触发脉冲到达,Communication Management 便会无参数调用 TriggerReceiveHandler [SWS_CM_00250]。在该处理程序内部,应用程序调用 GetNewTriggers() 以更新触发计数器并读取自上次调用以来到达的脉冲数 [SWS_CM_00226]。此时值 0 表示没有新脉冲。
  4. 终止:为了有序析构,应用程序调用 Unsubscribe() [SWS_CM_00810],并通过 UnsetReceiveHandler() [SWS_CM_11614] 以及 UnsetSubscriptionStateChangeHandler() [SWS_CM_01108] 移除已设置的处理程序。
触发信号处理流程应用Proxy TriggerCommunication ManagementSetReceiveHandler(handler)Subscribe()Abonnement anfordernUse Case: 触发事件到达handler() (TriggerReceiveHandler)GetNewTriggers()std::size_t(计数值)Use Case: BereinigungUnsubscribe()UnsetReceiveHandler()

时序图:从注册和订阅到信号接收再到注销的典型触发处理流程。来源:[SWS_CM_00226]、[SWS_CM_00250]、[SWS_CM_00723]、[SWS_CM_00810]、[SWS_CM_11614]。

错误场景

规范为接口方法定义了特定的违规条件(Violations)和异常安全性:

  • InvalidHandlerViolation:在 SetReceiveHandler() [SWS_CM_00250]、[SWS_CM_00352]、SetSubscriptionStateChangeHandler() [SWS_CM_01106]、[SWS_CM_01107] 或 SetTransportFaultConditionHandler() [SWS_CM_00106]、[SWS_CM_00107] 中传入无效或空 Callable 时发生。
  • InsufficientPermissionsViolation:在 Subscribe() 期间,当访问控制(Grant Enforcement)拒绝触发器订阅权限时触发 [SWS_CM_00723]。
  • E2E 保护中的传输错误:错误的传输状态通过使用 SetTransportFaultConditionHandler() 注册的处理程序报告 [SWS_CM_00106],[SWS_CM_00107],该处理程序可以通过 UnsetTransportFaultConditionHandler() 重新注销 [SWS_CM_00108]。
  • 异常安全性:几乎所有操作都被声明为 noexcept 且是异常安全的(exception safe)[SWS_CM_00226],[SWS_CM_00723]。一个例外是 UnsetReceiveHandler(),根据规范其被明确归类为非异常安全(not exception safe)[SWS_CM_11614];推测该调用在出错时可能会传播异常,或者需要在客户端应用程序中进行专门的错误处理。 问题 Q-3f9833ab71a91dd1 (未决)

本指南完全基于 AUTOSAR Adaptive R25-11 规范中针对 Communication Management 模块的内容。

成员图

类图

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

G n_SI_Namespace___proxy__triggers___Trigger_725 <Trigger> + SetTransportFaultConditionHandler() + UnsetTransportFaultConditionHandler() + GetNewTriggers() + GetSubscriptionState() + SetSubscriptionStateChangeHandler() + Subscribe() + UnsetSubscriptionStateChangeHandler() + Unsubscribe() + SetReceiveHandler() + UnsetReceiveHandler()

详细视图

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

方法

Method to update the trigger counter.

std::size_t GetNewTriggers () noexcept;

Query ara::com::SubscriptionState, as per [SWS_CM_00310].

ara::com::SubscriptionState GetSubscriptionState () const noexcept;

Trigger SetReceiveHandler

重载 SetReceiveHandler 2
void SetReceiveHandler (ara::com::TriggerReceiveHandler handler) noexcept; SWS_CM_00250
template <typename ExecutorT> void SetReceiveHandler (ara::com::TriggerReceiveHandler handler, ExecutorT &&executor) noexcept; SWS_CM_00352

As per [SWS_CM_01107] but the method shall execute in a provided context

重载 SetSubscriptionStateChangeHandler 2
template <typename ExecutorT> void SetSubscriptionStateChangeHandler (ara::com::SubscriptionState ChangeHandler handler, ExecutorT &&executor) noexcept; SWS_CM_01106
void SetSubscriptionStateChangeHandler (ara::com::SubscriptionState ChangeHandler handler) noexcept; SWS_CM_01107

Provides possibility to register a TransportFaultConditionHandler for a given Proxy Trigger.

重载 SetTransportFaultConditionHandler 2
void SetTransportFaultConditionHandler (ara::com::e2e::TransportFault ConditionHandler handler) noexcept; SWS_CM_00106
template <typename ExecutorT> void SetTransportFaultConditionHandler (ara::com::e2e::TransportFault ConditionHandler handler, ExecutorT &&executor) noexcept; SWS_CM_00107
Subscribe 函数

Method to subscribe to a service trigger. When called it starts a subscription of the corresponding Trigger. If the Trigger is already in state kSubscribed or in state kSubscriptionPending at the time of the call, and this method is invoked, it shall return without any action.

void Subscribe () noexcept;

Disable Trigger receive handler

void UnsetReceiveHandler ();

Unset ara::com::SubscriptionState change handler

void UnsetSubscriptionStateChangeHandler () noexcept;

Provides the possibility to unregister a previously set ara::com::e2e:: TransportFaultConditionHandler for a given Proxy Trigger.

void UnsetTransportFaultConditionHandler () noexcept;

Method to unsubscribe from a service trigger. If the Trigger is not subscribed to at the time of the call invoked, it shall return without any action.

void Unsubscribe () noexcept;

方法文档

函数 GetNewTriggers [SWS_CM_00226] Upstream: RS_CM_00202, RS_AP_00114, RS_AP_00120, RS_AP_00121, RS_AP_00127, RS_AP_00128, RS_AP_00139

std::size_t GetNewTriggers () noexcept;

Method to update the trigger counter.

Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Scopeclass <SI-Namespace>::proxy::triggers::<Trigger>
Exception-Sicherheitexception safe

Rückgabewert

TypBeschreibung
std::size_tThe number of triggers occurred since the last call to GetNew Triggers (a Zero value means that no new triggers have been received)

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

Record
AUTOSAR/AP/record/SWS_CM_00226
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_00226@rel:R25-11#7e3abe3e
Content hash
7e3abe3e
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_00226
Status: valid/unmigrated Version: rel:R25-11#f934d813 Versionshistorie & Revisions (1 transition, 6 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_CM_00226@rel:R25-11#f934d813
Point-in-Time History:
Recorded Revisions (6):
  • R25-11rel:R25-11#199cadc92026-09-30
  • R21-11rel:R21-11#cb20f15d2026-10-14
  • R22-11rel:R22-11#cb20f15d2026-10-14
  • R23-11rel:R23-11#7efe3ed62026-10-14
  • R24-11rel:R24-11#33fa04b82026-10-14
  • R25-11rel:R25-11#f934d8132026-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

函数 GetSubscriptionState [SWS_CM_01105] Upstream: RS_CM_00106

ara::com::SubscriptionState GetSubscriptionState () const noexcept;
Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Scopeclass <SI-Namespace>::proxy::triggers::<Trigger>
Exception-Sicherheitexception safe

Rückgabewert

TypBeschreibung
ara::com::SubscriptionStateThe state of the subscription.

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

Record
AUTOSAR/AP/record/SWS_CM_01105
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_01105@rel:R25-11#1aeb2035
Content hash
1aeb2035
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_01105
Status: valid/unmigrated Version: rel:R25-11#9a5b7923 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_CM_01105@rel:R25-11#9a5b7923
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

函数 SetReceiveHandler [SWS_CM_00250] Upstream: RS_CM_00203, RS_AP_00114, RS_AP_00120, RS_AP_00121

void SetReceiveHandler (ara::com::TriggerReceiveHandler handler) noexcept;

Trigger SetReceiveHandler

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

使用

函数SetReceiveHandler在服务代理(<SI-Namespace>::proxy::triggers::<Trigger>)的触发器类作用域中调用,并通过头文件<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h包含[SWS_CM_00250]。触发器与事件、方法和字段一起构成了ara::com中的四种通信机制之一EXP_ARAComAPI §4.2 “Means of Communication”。

类型为ara::com::TriggerReceiveHandler的参数handler接收一个可调用对象,当触发器到达时,Communication Management 会调用该对象。处理程序本身没有参数;要在回调函数内部查询当前触发器计数值,必须调用特定触发器类的GetNewTriggers方法[SWS_CM_00250]。

错误处理与异常安全性

该注册不返回任何返回值(void),并被定义为noexcept以及exception safe[SWS_CM_00250]。如果传入的 Callable 不存在或为null,则会发生形式为InvalidHandlerViolation的调用约定违规[SWS_CM_00250]。

交互与变体

针对需要在定义的执行上下文中处理触发器处理程序的场景,存在带有ExecutorT的模板重载[SWS_CM_00352]。在代理层级,也为事件([SWS_CM_00181]、[SWS_CM_11356])以及字段([SWS_CM_11605]、[SWS_CM_11611])提供了类似的回调注册方法EXP_ARAComAPI §5.3.1 “Proxy Class API’s”。

本使用说明由 AI 基于 AUTOSAR 规范生成。

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

Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Scopeclass <SI-Namespace>::proxy::triggers::<Trigger>
Exception-Sicherheitexception safe
Verletzungen (Violations)InvalidHandlerVio- Provided Callable handler does not exist or is null lation

Parameter (in)

ParameterBeschreibung
handlerThe handler that shall be called by Communication Management upon trigger arrival. The ara::com::TriggerReceiveHandler constitutes a function without parameters and has to use the Get NewTriggers method of the specific Trigger class to access the retrieved trigger counter. See [SWS_CM_00351] for it’s definition.

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_CM_00250
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_00250@rel:R25-11#3fc29b65
Content hash
3fc29b65
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_00250
Status: valid/unmigrated Version: rel:R25-11#999cd417 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_CM_00250@rel:R25-11#999cd417
Point-in-Time History:
Recorded Revisions (4):
  • R25-11rel:R25-11#a8f6c0c62026-09-30
  • R23-11rel:R23-11#8da588682026-10-14
  • R24-11rel:R24-11#c63fcde62026-10-14
  • R25-11rel:R25-11#999cd4172026-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

函数 SetReceiveHandler [SWS_CM_00352] Upstream: RS_CM_00211, RS_AP_00114, RS_AP_00120, RS_AP_00127, RS_AP_00128, RS_AP_00138

template <typename ExecutorT> void SetReceiveHandler (ara::com::TriggerReceiveHandler handler, ExecutorT &&executor) noexcept;

As per [SWS_CM_00250] but the method shall execute in a provided context

Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Scopeclass <SI-Namespace>::proxy::triggers::<Trigger>
Exception-Sicherheitexception safe
Verletzungen (Violations)InvalidHandlerVio- Provided Callable handler does not exist or is null lation

Template-Parameter

ParameterBeschreibung
ExecutorTAs per [SWS_CM_11360]

Parameter (in)

ParameterBeschreibung
handlerAs per [SWS_CM_00181]
executorAs per [SWS_CM_11360]

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_CM_00352
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_00352@rel:R25-11#d1b6be1d
Content hash
d1b6be1d
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_00352
Status: valid/unmigrated Version: rel:R25-11#7a0a39e7 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_CM_00352@rel:R25-11#7a0a39e7
Point-in-Time History:
Recorded Revisions (4):
  • R25-11rel:R25-11#774e38c12026-09-30
  • R23-11rel:R23-11#589034f42026-10-14
  • R24-11rel:R24-11#751a07032026-10-14
  • R25-11rel:R25-11#7a0a39e72026-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

函数 SetSubscriptionStateChangeHandler [SWS_CM_01106] Upstream: RS_CM_00106, RS_AP_00114, RS_AP_00120, RS_AP_00127, RS_AP_00128, RS_AP_00138

template <typename ExecutorT> void SetSubscriptionStateChangeHandler (ara::com::SubscriptionState ChangeHandler handler, ExecutorT &&executor) noexcept;

As per [SWS_CM_01107] but the method shall execute in a provided context

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

使用

作用域 <SI-Namespace>::proxy::triggers::<Trigger> 中的模板函数 SetSubscriptionStateChangeHandler 注册一个用于通知订阅状态变更([SWS_CM_01106])的回调。它通过头文件 <SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h 声明并接收两个参数:

  • handler:类型为 ara::com::SubscriptionStateChangeHandler 的可调用实体,应在状态变更时执行([SWS_CM_01107])。
  • executor:类型为 ExecutorT 的执行上下文([SWS_CM_11360]),处理程序的执行必须在该上下文中进行。

注册本身表现为同步且没有返回值(void)。注册的回调将在状态发生变更时在指定的执行上下文中执行。

错误处理与异常安全性

该方法声明为 noexcept 并指定为 exception safe([SWS_CM_01106])。如果传入的 Callable 实例不存在或为空,则存在 InvalidHandlerViolation([SWS_CM_01106])。由于不会抛出异常,无效的处理程序大概率会导致平台特定的错误路径(解读)。 问题 Q-cbb90bfbfa10338d (未决)

并发性与交互

通过传入 Executor([SWS_CM_11360]),应用程序自行控制状态回调的执行上下文。这应能防止长时间运行的处理程序调用阻塞通信管理的内部事件处理(解读)。 问题 (未决)该函数扩展了无上下文变体 [SWS_CM_01107],并构成了针对 Proxy 事件([SWS_CM_11354])、Proxy 字段([SWS_CM_11608])和 Skeleton 触发器([SWS_CM_11111])的基于 Executor 的接口的触发器对等项。

此使用说明为自动生成,基于 AUTOSAR Adaptive Platform 规范。

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

Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Scopeclass <SI-Namespace>::proxy::triggers::<Trigger>
Exception-Sicherheitexception safe
Verletzungen (Violations)InvalidHandlerVio- Provided Callable handler does not exist or is null lation

Template-Parameter

ParameterBeschreibung
ExecutorTAs per [SWS_CM_11360]

Parameter (in)

ParameterBeschreibung
handlerAs per [SWS_CM_01107]
executorAs per [SWS_CM_11360]

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_CM_01106
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_01106@rel:R25-11#a2bbde4b
Content hash
a2bbde4b
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_01106
Status: valid/unmigrated Version: rel:R25-11#c7808b12 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_CM_01106@rel:R25-11#c7808b12
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

函数 SetSubscriptionStateChangeHandler [SWS_CM_01107] Upstream: RS_CM_00106

void SetSubscriptionStateChangeHandler (ara::com::SubscriptionState ChangeHandler handler) noexcept;

Set ara::com::SubscriptionState change handler

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

使用函数 [SWS_CM_01107] 可以在触发器的 Proxy 作用域(<SI-Namespace>::proxy::triggers::<Trigger>)中注册一个回调处理程序,Communication Management 会在每次订阅状态(ara::com::SubscriptionState)发生变更时调用该程序。该函数没有返回值,且被指定为异常安全(noexcept)。

由于订阅原则上必须作为异步过程来处理,因此应用程序只有在通过 [SWS_CM_01107] 注册的处理程序或查询函数 GetSubscriptionState() 报告状态 kSubscribed 时,方可认为订阅成功 [SWS_CM_12006]。当出现时间延迟,或者服务器由于重启或网络问题而暂时不可用时,Communication Management 会激活带有状态 kSubscriptionPending 的处理程序 [SWS_CM_00313]。

对于错误处理和集成,适用以下边界条件:

  • 错误处理:传递不存在或空的可调用对象(null)是不允许的,并会导致 InvalidHandlerViolation [SWS_CM_01107]。
  • 执行上下文:如果处理程序不应在默认上下文中执行,而是在特定的执行上下文中执行,则可以使用带有 ExecutorT&& 的模板重载 [SWS_CM_01106]。
  • 相互协作:对于服务事件,在常规 Proxy 类 API 框架下存在类似接口 [SWS_CM_00333] ARAComAPI §5.3.1 “Proxy Class API’s”。

本使用说明基于 AUTOSAR R25-11 规范自动生成。

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

Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Scopeclass <SI-Namespace>::proxy::triggers::<Trigger>
Exception-Sicherheitexception safe
Verletzungen (Violations)InvalidHandlerVio- Provided Callable handler does not exist or is null lation

Parameter (in)

ParameterBeschreibung
handlerThe handler that shall be called by Communication Management when the ara::com::SubscriptionState of the event has changed.

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_CM_01107
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_01107@rel:R25-11#e1633b6c
Content hash
e1633b6c
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_01107
Status: valid/unmigrated Version: rel:R25-11#465350f1 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_CM_01107@rel:R25-11#465350f1
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

函数 SetTransportFaultConditionHandler [SWS_CM_00106] Upstream: RS_CM_00224, RS_E2E_08534

void SetTransportFaultConditionHandler (ara::com::e2e::TransportFault ConditionHandler handler) noexcept;

Provides possibility to register a TransportFaultConditionHandler for a given Proxy Trigger.

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

函数 SetTransportFaultConditionHandler 用于在 proxy::triggers::<Trigger> 的实例上注册类型为 ara::com::e2e::TransportFaultConditionHandler 的回调函数([SWS_CM_00106])。它接收参数 handler,没有返回值,并被指定为 noexcept 以及 exception safe([SWS_CM_00106])。

通信层通过注册的处理程序指示已识别出的传输层错误。在 DDS 网络绑定中,处理程序将底层 DataReader 实体的事件报告为 TransportFaultCondition([SWS_CM_00212]):

  • 在样本被丢弃(例如由于内存短缺或数据损坏)时为 TransportFaultCondition::kSampleRejected,
  • 在违反接收截止时间时为 TransportFaultCondition::kDeadlineMissed(REQUESTED_DEADLINE_MISSED),
  • 在丢失已识别的数据样本时为 TransportFaultCondition::kSampleLost([SWS_CM_00212])。

如果传递了不存在或空的处理程序而不是有效的可调用对象,则运行时环境报告 InvalidHandlerViolation([SWS_CM_00106])。由于函数签名声明为 noexcept,因此该违规行为推测会导致平台端错误处理,而不是 C++ 异常。 问题 Q-ebaf44b8f7b198e8 (未决)

注册在调用方的上下文中同步执行;在此重载中,处理程序的执行不会委托给特定的分发器。如果回调应在定义的执行上下文中运行,则可以使用带有附加 ExecutorT&& 的重载模板变体([SWS_CM_00107])。绑定通常在实际触发器处理之前进行,以便从一开始就捕获错误。 问题 (未决)

针对 TransportFaultConditionHandler 的相应注册选项同样存在于 Proxy 事件([SWS_CM_00099])、Proxy 字段([SWS_CM_00109])以及 Skeleton 方法([SWS_CM_00093])和 Skeleton 字段([SWS_CM_00096])。

本段文本由人工智能生成,仅供参考。具有约束力的是所引用的 AUTOSAR 规范。

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

Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Scopeclass <SI-Namespace>::proxy::triggers::<Trigger>
Exception-Sicherheitexception safe
Verletzungen (Violations)InvalidHandlerVio- Provided Callable handler does not exist or is null lation

Parameter (in)

ParameterBeschreibung
handlerHandler of type TransportFaultConditionHandler to be set

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_CM_00106
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_00106@rel:R25-11#cab89e54
Content hash
cab89e54
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_00106
Status: valid/unmigrated Version: rel:R25-11#a6d4504c Versionshistorie & Revisions (1 transition, 3 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_CM_00106@rel:R25-11#a6d4504c
Point-in-Time History:
Recorded Revisions (3):
  • R25-11rel:R25-11#8276dedf2026-09-30
  • R24-11rel:R24-11#807777b02026-10-14
  • R25-11rel:R25-11#a6d4504c2026-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

函数 SetTransportFaultConditionHandler [SWS_CM_00107] Upstream: RS_CM_00224, RS_E2E_08534

template <typename ExecutorT> void SetTransportFaultConditionHandler (ara::com::e2e::TransportFault ConditionHandler handler, ExecutorT &&executor) noexcept;

Execution Context overload for hierarchicalnamespacelistlowerproxy::proxy:: triggers::triggername::SetTransportFaultConditionHandler for a given Proxy Trigger.

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

函数[SWS_CM_00107]用于在命名空间<SI-Namespace>::proxy::triggers::<Trigger>中注册代理触发器传输错误的回调例程。作为带有执行上下文的重载,除了类型为ara::com::e2e::TransportFaultConditionHandler的处理程序之外,它还接收一个执行器对象executor,触发的异步计算将在该执行器对象中执行。

关于使用和错误处理,适用以下规定:

  • 参数和返回值:参数handler传递要设置的可调用对象(Callable),而executor定义异步任务的执行上下文[SWS_CM_00107]。该函数不返回任何返回值,并被声明为noexcept(异常安全性:exception safe)。
  • 错误情况和违规:如果传递了不存在或无效的处理程序(null),运行时将报告一个InvalidHandlerViolation[SWS_CM_00107]。
  • 报告的错误状态:注册的处理程序接收符合[SWS_CM_00212]的已检测传输错误。其中包括TransportFaultCondition::kSampleRejected(例如发生数据损坏或资源不足时)、TransportFaultCondition::kDeadlineMissed(发生截止时间违规时)以及TransportFaultCondition::kSampleLost(发生样本丢失时)。

与不带执行器的基本函数[SWS_CM_00106]相比,该变体允许针对触发器的错误处理定向控制并发上下文。在通信管理中,针对代理事件[SWS_CM_00100]、代理字段[SWS_CM_00110],以及在骨架层级针对方法[SWS_CM_00094]和字段[SWS_CM_00097],均存在带有执行上下文的类似重载。

本使用说明基于 AUTOSAR Adaptive Platform R25-11 规范自动生成。

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

Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Scopeclass <SI-Namespace>::proxy::triggers::<Trigger>
Exception-Sicherheitexception safe
Verletzungen (Violations)InvalidHandlerVio- Provided Callable handler does not exist or is null lation

Parameter (in)

ParameterBeschreibung
handlerHandler to be set
executorExecutor object in which any asynchronous computation spawn shall be invoked

Rückgabewert

TypBeschreibung
None
Siehe auch: [SWS_CM_00106]

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

Record
AUTOSAR/AP/record/SWS_CM_00107
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_00107@rel:R25-11#f75400e7
Content hash
f75400e7
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_00107
Status: valid/unmigrated Version: rel:R25-11#b77dbb3c Versionshistorie & Revisions (1 transition, 3 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_CM_00107@rel:R25-11#b77dbb3c
Point-in-Time History:
Recorded Revisions (3):
  • R25-11rel:R25-11#ed4541552026-09-30
  • R24-11rel:R24-11#eeb2c97a2026-10-14
  • R25-11rel:R25-11#b77dbb3c2026-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

函数 Subscribe [SWS_CM_00723] Upstream: RS_CM_00103, RS_AP_00114, RS_AP_00120

void Subscribe () noexcept;

Method to subscribe to a service trigger. When called it starts a subscription of the corresponding Trigger. If the Trigger is already in state kSubscribed or in state kSubscriptionPending at the time of the call, and this method is invoked, it shall return without any action.

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

方法 Subscribe 用于通过命名空间 <SI-Namespace>::proxy::triggers::<Trigger> 中的Proxy实例在客户端订阅服务Trigger [SWS_CM_00723]。在使用之前,服务实例必须已在服务端通过 OfferService() 提供,并由客户端通过Service Discovery机制查找到 AUTOSAR_AP_EXP_ARAComAPI §4.2 “Means of Communication”。

与Event订阅([SWS_CM_00141])和Field订阅([SWS_CM_11601])相比,用于Trigger的 Subscribe 具有以下特定属性:

对于生命周期和错误处理,适用以下条件:

  • 状态检查与幂等性:如果在调用时Trigger已处于状态 kSubscribed 或 kSubscriptionPending,则该方法立即返回且不执行进一步操作 [SWS_CM_00723]。
  • 异常安全性:该函数被指定为 noexcept 和 exception safe [SWS_CM_00723]。
  • 访问控制:权限不足时,授权执行(Grant-Enforcement)将拒绝执行并引发 InsufficientPermissionsViolation [SWS_CM_00723]。

此使用说明由AI生成,且仅基于AUTOSAR Adaptive R25-11中的规范要求。

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

Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Scopeclass <SI-Namespace>::proxy::triggers::<Trigger>
Exception-Sicherheitexception safe
Verletzungen (Violations)InsufficientPer- Refused by Grant Enforcement missionsViolation

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_CM_00723
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_00723@rel:R25-11#8087f778
Content hash
8087f778
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_00723
Status: valid/unmigrated Version: rel:R25-11#c781043c Versionshistorie & Revisions (1 transition, 6 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_CM_00723@rel:R25-11#c781043c
Point-in-Time History:
Recorded Revisions (6):
  • R25-11rel:R25-11#efea6fd02026-09-30
  • R21-11rel:R21-11#3e3032682026-10-14
  • R22-11rel:R22-11#3e3032682026-10-14
  • R23-11rel:R23-11#91a4b8412026-10-14
  • R24-11rel:R24-11#0233787d2026-10-14
  • R25-11rel:R25-11#c781043c2026-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

函数 UnsetReceiveHandler [SWS_CM_11614] Upstream: RS_CM_00203

void UnsetReceiveHandler ();

Disable Trigger receive handler

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

使用

命名空间 <SI-Namespace>::proxy::triggers::<Trigger> 中的同步函数 UnsetReceiveHandler 用于在 Proxy 端停用先前注册的服务触发器接收处理程序 [SWS_CM_11614]。该函数需要包含头文件 #include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h",不接收任何传入参数且没有返回值。

通过调用此函数,将注销应用程序特定的回调。这允许应用程序在事件驱动接收和基于查询的模型(轮询)之间灵活切换(AUTOSAR_AP_EXP_ARAComAPI 第46页,AUTOSAR_AP_SWS_CommunicationManagement §7.5.18.1)。

错误处理与异常安全性

与服务事件 [SWS_CM_00183] 和服务字段 [SWS_CM_11606] 的类似函数(它们明确被指定为 noexcept 且异常安全)不同,针对触发器的 UnsetReceiveHandler 被声明为非异常安全(not exception safe)[SWS_CM_11614]。解释:调用方应当做好准备,即当通信基础设施发生内部错误时可能会抛出异常,尽管标准中并未列出具体的异常类型或错误码。 问题 Q-92e16243a7ddee35 (未决)

相互协作与绑定

该方法是 Proxy 命名空间中触发器类的组成部分(AUTOSAR_AP_EXP_ARAComAPI §5.3.1)。当使用 DDS 绑定时,根据 [SWS_CM_11141],该方法调用通过关联的 DataReader 按照 [SWS_CM_11026] 中规定的规则进行映射。

本使用说明系自动创建,且完全基于 AUTOSAR Adaptive Release R25-11 规范。

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

Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Scopeclass <SI-Namespace>::proxy::triggers::<Trigger>
Exception-Sicherheitnot exception safe

Rückgabewert

TypBeschreibung
None
Siehe auch: [SWS_CM_00183]

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

Record
AUTOSAR/AP/record/SWS_CM_11614
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_11614@rel:R25-11#c9dbbe38
Content hash
c9dbbe38
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_11614
Status: valid/unmigrated Version: rel:R25-11#bbdaf9e4 Versionshistorie & Revisions (1 transition, 3 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_CM_11614@rel:R25-11#bbdaf9e4
Point-in-Time History:
Recorded Revisions (3):
  • R25-11rel:R25-11#5e7e170f2026-09-30
  • R24-11rel:R24-11#34cc39122026-10-14
  • R25-11rel:R25-11#bbdaf9e42026-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

函数 UnsetSubscriptionStateChangeHandler [SWS_CM_01108] Upstream: RS_CM_00106, RS_AP_00114, RS_AP_00120

void UnsetSubscriptionStateChangeHandler () noexcept;

Unset ara::com::SubscriptionState change handler

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

函数 UnsetSubscriptionStateChangeHandler 在客户端用于移除先前为触发器的订阅状态变更(ara::com::SubscriptionState)注册的回调 [SWS_CM_01108]。它声明在作用域 <SI-Namespace>::proxy::triggers::<Trigger> 中,并通过头文件 #include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h" 包含 [SWS_CM_01108]。

用法与调用上下文

该方法具有签名 void UnsetSubscriptionStateChangeHandler () noexcept;,不接收任何传入参数且不返回任何值 [SWS_CM_01108]。它在 Proxy 类的相应触发器实例上同步调用,以再次退订订阅状态变更时的通知 AUTOSAR_AP_EXP_ARAComAPI §5.3.1 “Proxy Class API’s”。解读:执行调用后,应不再向先前的处理程序传递任何进一步的状态变更。 问题 Q-d08dc975aacba85c (未决)

错误处理与并发

该接口声明为 noexcept,并显式指定为异常安全(exception safe)[SWS_CM_01108]。因此排除了调用失败或抛出异常的可能性,且不存在错误返回值。

相互作用

该函数契合 Proxy 接口的统一样式。在 Proxy 上下文中,针对事件(依据 [SWS_CM_00334] AUTOSAR_AP_SWS_CommunicationManagement §8.3.2.2.4.5 “UnsetSubscriptionStateChangeHandler”)以及针对字段(依据 [SWS_CM_11609] AUTOSAR_AP_SWS_CommunicationManagement §8.3.3.2.4.5 “UnsetSubscriptionStateChangeHandler”)提供了类似的注销方法。在服务器端或 Skeleton 端,存在用于触发器 [SWS_CM_01112] 和事件 [SWS_CM_12010] 的相应对等项。

本文本由 AI 生成,用作 AUTOSAR 规范范围内的参考指南。

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

Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Scopeclass <SI-Namespace>::proxy::triggers::<Trigger>
Exception-Sicherheitexception safe

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_CM_01108
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_01108@rel:R25-11#88d1e833
Content hash
88d1e833
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_01108
Status: valid/unmigrated Version: rel:R25-11#ed939965 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_CM_01108@rel:R25-11#ed939965
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

函数 UnsetTransportFaultConditionHandler [SWS_CM_00108] Upstream: RS_CM_00224, RS_E2E_08534

void UnsetTransportFaultConditionHandler () noexcept;

Provides the possibility to unregister a previously set ara::com::e2e:: TransportFaultConditionHandler for a given Proxy Trigger.

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

函数 UnsetTransportFaultConditionHandler 用于重新注销先前为特定代理触发器注册的 ara::com::e2e::TransportFaultConditionHandler([SWS_CM_00108],记录在 AUTOSAR_AP_SWS_CommunicationManagement §8.3.7.1.1.3 “UnsetTransportFaultConditionHandler” 中)。它位于命名空间 <SI-Namespace>::proxy::triggers::<Trigger> 中,并通过头文件 #include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h" 引入([SWS_CM_00108])。

签名是 void UnsetTransportFaultConditionHandler() noexcept;。该调用不接受任何参数,且不返回任何返回值([SWS_CM_00108])。通过 noexcept 声明和归类为 exception safe,该函数在正常运行时不抛出异常([SWS_CM_00108])。规范中未规定特定的错误代码、错误通道或回退值。

关于流程,该函数同步解除与错误处理例程的关联;因此,成功执行后,针对受影响触发器的 E2E 传输错误通知大概不会再传递给先前的 Handler(Interpretation)。 问题 Q-ae8477bc6530e352 (未决)

在整个系统的框架内,该元素构成了 AUTOSAR_AP_SWS_CommunicationManagement §8.3/8.4 中针对其他通信模式的类似注销函数的对应项:

  • 代理事件:事件层级上的 UnsetTransportFaultConditionHandler([SWS_CM_00105])。
  • 代理字段:字段通知器的注销([SWS_CM_00126])。
  • Skeleton 层级:字段 Get/Set 的注销([SWS_CM_00098])以及 Skeleton 所有方法的注销([SWS_CM_00095])。

本使用说明基于 AUTOSAR R25-11 自动生成。

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

Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Scopeclass <SI-Namespace>::proxy::triggers::<Trigger>
Exception-Sicherheitexception safe

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_CM_00108
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_00108@rel:R25-11#e75b1def
Content hash
e75b1def
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_00108
Status: valid/unmigrated Version: rel:R25-11#5766b8c1 Versionshistorie & Revisions (1 transition, 3 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_CM_00108@rel:R25-11#5766b8c1
Point-in-Time History:
Recorded Revisions (3):
  • R25-11rel:R25-11#b0faf65e2026-09-30
  • R24-11rel:R24-11#a251c51a2026-10-14
  • R25-11rel:R25-11#5766b8c12026-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

函数 Unsubscribe [SWS_CM_00810] Upstream: RS_CM_00103, RS_AP_00114, RS_AP_00120

void Unsubscribe () noexcept;

Method to unsubscribe from a service trigger. If the Trigger is not subscribed to at the time of the call invoked, it shall return without any action.

Header-Datei#include "<SiNamespaceDerivedDirectoryPath>/<SiShortname>_proxy.h"
Scopeclass <SI-Namespace>::proxy::triggers::<Trigger>
Exception-Sicherheitexception safe

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_CM_00810
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_00810@rel:R25-11#8d2fdf82
Content hash
8d2fdf82
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_00810
Status: valid/unmigrated Version: rel:R25-11#270e3cc7 Versionshistorie & Revisions (1 transition, 6 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_CM_00810@rel:R25-11#270e3cc7
Point-in-Time History:
Recorded Revisions (6):
  • R25-11rel:R25-11#d20f32f52026-09-30
  • R21-11rel:R21-11#d12e778e2026-10-14
  • R22-11rel:R22-11#d12e778e2026-10-14
  • R23-11rel:R23-11#d12e778e2026-10-14
  • R24-11rel:R24-11#037f29922026-10-14
  • R25-11rel:R25-11#270e3cc72026-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