DEENESPTFRRUARHIKOZHNL

类 ara::diag::SovdProximityChallenge

[SWS_DM_01481] Upstream: RS_Diag_04262

class SovdProximityChallenge {...};

Class to implement the SOVD proximity_challenge interfaces in the application.

Header-Datei#include "ara/diag/sovd_proximity_challenge.h"
Forwarding-Header#include "ara/diag/diag_fwd.h"
Scopenamespace ara::diag

用户指南人工智能生成

使应用程序能够为受保护的 SOVD 诊断操作生成并验证邻近性证明。
AI 生成 未审核 模型: gemini-3.8-flash-medium · 推理强度: medium · 温度: 不可控 · 提示词: 7c7c088635a6 来源 未决问题(2)
译自德文指南gemini-3.8-flash-low · 2026-10-13 · 德文原文

使应用程序能够为受保护的 SOVD 诊断操作生成并验证邻近性证明。

该接口类在 AUTOSAR Adaptive Platform 中用于实现诊断环境中 SOVD 操作的邻近性检查 [SWS_DM_01481]。应用程序继承自该类,通过 Offer() 激活 Diagnostic Management 的转发,并异步提供所需的 Challenge 及其后续验证 [SWS_DM_01478]。对验证方法的并发调用取决于构造时选择的并发模式,而注册和析构不是线程安全的。

上下文

类 ara::diag::SovdProximityChallenge [SWS_DM_01481] 在 AUTOSAR Adaptive Platform 中用于在 Service-Oriented Vehicle Diagnostics (SOVD) 环境下由应用程序端实现邻近性证明(Proximity Challenge)接口。它在 AUTOSAR Diagnostic Management(DM 或 Diagnostic Server)与提供物理或加密邻近性检查安全逻辑的实际车辆应用程序之间架起桥梁 AUTOSAR_AP_SWS_Diagnostics §8.56 “Providing the SOVD operation proximity_challenge”。如果为某个 SOVD 操作配置了需要邻近性证明(属性 proximityProofRequired 为 TRUE),则 Diagnostic Management 在处理诊断请求时向应用程序请求 Challenge,并对客户端返回的响应进行验证 [SWS_DM_01398]。该联合体涉及三个主要参与方:外部 SOVD 客户端、起中介作用的 Diagnostic Management 以及使用该功能的应用程序。

context client SOVD-Client dm Diagnostic Management (Diagnostic Server) client->dm SOVD-Operationsanfrage client->dm 带有 proximity_response 的请求 dm->client 带有 proximity_challenge 的响应 app Applikation (SovdProximityChallenge) dm->app GetChallenge / ValidateResponse app->dm Challenge / Validierungsergebnis

上下文图:SOVD 客户端、Diagnostic Management 与应用程序类 ara::diag::SovdProximityChallenge 之间的相互作用。来源:[SWS_DM_01398]、[SWS_DM_01481]、AUTOSAR_AP_SWS_Diagnostics §8.56 “Providing the SOVD operation proximity_challenge”。

生命周期

Handler 类的实例化通过构造函数 SovdProximityChallenge [SWS_DM_01480] 进行。该构造函数将实例绑定到清单中定义的 ara::core::InstanceSpecifier,并通过参数 ConcurrencyType 指定后续执行是并发(kConcurrent)还是顺序(kNotConcurrent)进行。构造函数本身被规范为线程安全的 [SWS_DM_01480]。对象创建后,Handler 最初处于被动状态。只有通过显式调用 Offer() [SWS_DM_01478],Diagnostic Management 才被授权将请求转发给应用程序实例。

可以随时通过 StopOffer() [SWS_DM_01495] 再次停用转发。Offer()、StopOffer() 以及虚析构函数 ~SovdProximityChallenge() [SWS_DM_01479] 都不是线程安全的。解释:在销毁对象之前,可能需要调用 StopOffer(),以防止转发给正在析构的对象。 问题 Q-b4c66854163f433e (未决)此外,在实践中,应用程序实例通常在诊断过程的整个运行时间内保持存在,以便持续保护 SOVD 操作。实际查询和验证方法 GetChallenge() [SWS_DM_01494] 与 ValidateResponse() [SWS_DM_01493] 的线程安全性由构造函数中传入的 ConcurrencyType 控制。

使用路径

在通过 Offer() [SWS_DM_01478] 成功初始化并提供服务后,该类开始响应 Diagnostic Management 的请求。如果 SOVD 客户端请求受保护的操作,DM 将调用纯虚方法 GetChallenge() [SWS_DM_01494]。应用程序生成近程令牌,并通过 ara::core::Future<SovdProximityChallengeType> 异步返回该令牌及有效截止时间(valid_until)[SWS_DM_01494]。默认情况下,假定在任何时间点仅存在一个对所有客户端和操作均有效的 Challenge,且其生存期通常固定设定(例如两分钟)AUTOSAR_AP_SWS_Diagnostics §8.56 “Providing the SOVD operation proximity_challenge”。对于更复杂的场景,应用程序可以评估传入的 ara::diag::MetaInfo 对象,以执行特定于客户端或操作的检查 AUTOSAR_AP_SWS_Diagnostics §8.56 “Providing the SOVD operation proximity_challenge”。

Diagnostic Management 在响应体中将属性 proximity_challenge 传输给客户端 [SWS_DM_01398]。如果客户端以近程证明做出响应,DM 将通过 ValidateResponse() [SWS_DM_01493] 转发这些数据。传入的内存区域 proximityResponse 保持有效,直到返回的 ara::core::Future<ProximityChallengeValidationResultType> 被满足或处理被中止 [SWS_DM_01493]。在进程关闭之前,通过 StopOffer() [SWS_DM_01495] 注销服务。

SOVD 接近度检查的调用流程SOVD-Client诊断管理ApplikationUse Case: DienstregistrierungOffer()Result<void>Use Case: Challenge anfordernSOVD-Operation anfordernGetChallenge(metaInfo)Future<SovdProximityChallengeType>带有 proximity_challenge 的响应Use Case: Antwort validieren带有 proximity_response 的 SOVD 请求ValidateResponse(proximityResponse, metaInfo)Future<ProximityChallengeValidationResultType>Use Case: Dienst deregistrierenStopOffer()

时序图:从提供、Challenge 获取和响应验证到服务注销的调用序列。来源:[SWS_DM_01478]、[SWS_DM_01494]、[SWS_DM_01493]、[SWS_DM_01495]、[SWS_DM_01398]。

错误场景

在通过构造函数 [SWS_DM_01480] 创建对象时,框架就会检查模型一致性,并可能报告以下违规情况:InstanceSpecifierMappingIntegrityViolation(标识符无法解析或未指向端口原型)、PortInterfaceMappingViolation(端口原型未被类型化为 DiagnosticSovdProximityChallengeInterface)、ProcessMappingViolation(未找到匹配的模型化进程)或 InstanceSpecifierAlreadyInUseViolation(标识符已在进程中使用)[SWS_DM_01480]。

在调用 Offer() [SWS_DM_01478] 时,返回的 ara::core::Result<void> 在发生错误时提供标准化错误代码:如果该端口已处于主动提供服务状态,则返回 DiagOfferErrc::kAlreadyOffered;如果 Monitor 配置与 DEXT 不一致,则返回 DiagOfferErrc::kConfigurationMismatch。对于 GetChallenge() [SWS_DM_01494] 和 ValidateResponse() [SWS_DM_01493],未定义标准化错误代码。该类的所有成员函数均声明为 noexcept 并保证异常安全性。

本指南基于 AUTOSAR Adaptive Platform 规范 Release R25-11。

成员图

类图

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

G nara__diag__SovdProximityChallenge981 SovdProximityChallenge + ~SovdProximityChallenge() + SovdProximityChallenge() + GetChallenge() + Offer() + StopOffer() + ValidateResponse()

详细视图

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

构造函数和析构函数

Constructs the port for SOVD proximity_challenge interface.

explicit SovdProximityChallenge (ara::core::InstanceSpecifier instance Specifier, ConcurrencyType concurrencyType) noexcept;

Destructor of SovdProximityChallenge.

virtual ~SovdProximityChallenge () noexcept;

方法

This function returns a proximity_challenge for the client.

virtual ara::core::Future< SovdProximityChallengeType > GetChallenge (const MetaInfo &metaInfo) noexcept=0;
Offer 函数

This Offer will enable the DM to forward request messages to this handler.

ara::core::Result< void > Offer () noexcept;
StopOffer 函数

This StopOffer will disable the forwarding of request messages from DM.

void StopOffer () noexcept;

This function validates the proximity response sent by the client.

virtual ara::core::Future< ProximityChallengeValidationResultType > ValidateResponse (ara::core::Span< const ara::core::Byte > proximity Response, const MetaInfo &metaInfo) noexcept=0;

方法文档

函数 GetChallenge [SWS_DM_01494] Upstream: RS_Diag_04262

virtual ara::core::Future< SovdProximityChallengeType > GetChallenge (const MetaInfo &metaInfo) noexcept=0;

This function returns a proximity_challenge for the client.

Header-Datei#include "ara/diag/sovd_proximity_challenge.h"
Scopeclass ara::diag::SovdProximityChallenge
Exception-Sicherheitexception safe
Thread-Sicherheitconditional whether the function has to be implemented thread safe or non-thread safe is determined by the ConcurrencyType given in the constructor

Parameter (in)

ParameterBeschreibung
metaInfoThe meta information of a diagnostic service port

Rückgabewert

TypBeschreibung
ara::core::Future< SovdProximityChallengeType>Challenge created by the application and point in time until when the challenge is valid (valid_until)

Fehler

FehlercodeBeschreibung
This function does not specify any standardized errors.

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

Record
AUTOSAR/AP/record/SWS_DM_01494
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01494@rel:R25-11#8fcf474c
Content hash
8fcf474c
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01494
Status: valid/unmigrated Version: rel:R25-11#7da8890a Versionshistorie & Revisions (1 transition, 5 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_DM_01494@rel:R25-11#7da8890a
Point-in-Time History:
Recorded Revisions (5):
  • R25-11rel:R25-11#3932f83c2026-09-30
  • R22-11rel:R22-11#2e1e945e2026-10-14
  • R23-11rel:R23-11#6b7e02122026-10-14
  • R24-11rel:R24-11#fa8c49c12026-10-14
  • R25-11rel:R25-11#7da8890a2026-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

函数 Offer [SWS_DM_01478] Upstream: RS_Diag_04262

ara::core::Result< void > Offer () noexcept;

This Offer will enable the DM to forward request messages to this handler.

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

类 ara::diag::SovdProximityChallenge(定义于 #include "ara/diag/sovd_proximity_challenge.h")的同步方法 Offer 将处理程序注册到 Diagnostic Management (DM),并使其能够将传入的请求消息(request messages)转发给处理程序实例 [SWS_DM_01478]。该调用无参数,并被指定为 noexcept [SWS_DM_01478]。

返回值采用 ara::core::Result<void> [SWS_DM_01478]。在出错时,该方法返回具有回滚语义的特定错误代码 [SWS_DM_01478]:

  • DiagOfferErrc::kAlreadyOffered:服务已通过该实例提供 [SWS_DM_01478]。
  • DiagOfferErrc::kConfigurationMismatch:处理程序的配置与 DEXT 数据不一致 [SWS_DM_01478]。

关于执行安全性,该方法声明为 exception safe,但明确视为 not thread-safe [SWS_DM_01478]。因此,对同一实例的并行调用必须由调用方应用程序进行同步。该提供模式符合 DM 处理程序的统一激活原则,正如其同样应用于 ara::diag::GenericRoutine [SWS_DM_00557]、ara::diag::GenericUDSService [SWS_DM_00619] 以及 ara::diag::CommunicationControl [SWS_DM_00809] 等场景。解释:在 Offer 成功执行之前,DM 推测不会将邻近挑战(Proximity-Challenge)的请求转发给处理程序。 问题 Q-320a80aca81ef460 (未决)

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

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

Header-Datei#include "ara/diag/sovd_proximity_challenge.h"
Scopeclass ara::diag::SovdProximityChallenge
Exception-Sicherheitexception safe
Thread-Sicherheitnot thread-safe

Rückgabewert

TypBeschreibung
ara::core::Result< void >Returns nothing or an error.

Fehler

FehlercodeBeschreibung
DiagOfferErrc::kAlreadyOfferedrollback_semantics The service is already offered.
DiagOfferErrc::kConfigurationMismatchrollback_semantics monitor configuration does not match DEXT

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

Record
AUTOSAR/AP/record/SWS_DM_01478
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01478@rel:R25-11#9b74eadf
Content hash
9b74eadf
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01478
Status: valid/unmigrated Version: rel:R25-11#6f4dc41d Versionshistorie & Revisions (1 transition, 5 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_DM_01478@rel:R25-11#6f4dc41d
Point-in-Time History:
Recorded Revisions (5):
  • R25-11rel:R25-11#ba32f38d2026-09-30
  • R22-11rel:R22-11#fbdd6a312026-10-14
  • R23-11rel:R23-11#7b9eb3952026-10-14
  • R24-11rel:R24-11#b44bdc532026-10-14
  • R25-11rel:R25-11#6f4dc41d2026-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

函数 SovdProximityChallenge [SWS_DM_01480] Upstream: RS_Diag_04262, RS_AP_00170, RS_AP_00171, RS_AP_00172, RS_AP_00173

explicit SovdProximityChallenge (ara::core::InstanceSpecifier instance Specifier, ConcurrencyType concurrencyType) noexcept;

Constructs the port for SOVD proximity_challenge interface.

Header-Datei#include "ara/diag/sovd_proximity_challenge.h"
Scopeclass ara::diag::SovdProximityChallenge
Exception-Sicherheitexception safe
Thread-Sicherheitthread-safe
Verletzungen (Violations)InstanceSpeci- InstanceSpecifier either cannot be resolved in the model in the fierMappingIn- context of your executable, or it refers to a model element other tegrityViolation than a PortPrototype. PortInterfaceMap- A PortPrototype that is referenced by a pingViolation DiagnosticSovdProximityChallengePortMapping needs to be typed by a DiagnosticSovdProximityChallengeInterface. ProcessMappingVio- Matching InstanceRef exists, but no matching (modelled) Process lation found that matches the (runtime) process. InstanceSpecifier- Violation message that is sent in case a constructor in the ara AlreadyInUseViola- framework was called with an InstanceSpecifier already in use in tion this process.

Parameter (in)

ParameterBeschreibung
instanceSpecifierInstanceSpecifier to a PortPrototype of a DiagnosticSovdProximityChallengeInterface service instance in the manifest.
concurrencyTypeSpecifies if the interface is implemented as thread safe ( kConcurrent) or non-thread safe (kNotConcurrent).

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

Record
AUTOSAR/AP/record/SWS_DM_01480
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01480@rel:R25-11#b3cdcf89
Content hash
b3cdcf89
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01480
Status: valid/unmigrated Version: rel:R25-11#935043cf Versionshistorie & Revisions (1 transition, 5 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_DM_01480@rel:R25-11#935043cf
Point-in-Time History:
Recorded Revisions (5):
  • R25-11rel:R25-11#ee8483be2026-09-30
  • R22-11rel:R22-11#1878db142026-10-14
  • R23-11rel:R23-11#fb8a0a8f2026-10-14
  • R24-11rel:R24-11#e6beb5542026-10-14
  • R25-11rel:R25-11#935043cf2026-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

函数 StopOffer [SWS_DM_01495] Upstream: RS_Diag_04262

void StopOffer () noexcept;

This StopOffer will disable the forwarding of request messages from DM.

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

类 ara::diag::SovdProximityChallenge 的方法 StopOffer 停用从 Diagnostic Management (DM) 向此服务实例转发请求消息的功能([SWS_DM_01495])。该接口通过头文件 ara/diag/sovd_proximity_challenge.h 提供。

使用和执行上下文

该函数被同步调用,不接受传入参数,且没有返回值([SWS_DM_01495])。执行后,DM 不再向应用程序转发有关邻近挑战的进一步请求。

错误处理与异常安全性

该方法声明为 noexcept,且完全异常安全(exception safe)([SWS_DM_01495])。未针对此调用定义错误状态或特定错误代码。

并发性与生命周期

关于执行,StopOffer 被明确指定为非线程安全(not thread-safe)([SWS_DM_01495])。在同一实例上的并行调用必须在调用方进行同步。解释:此调用通常可能在组件关闭或邻近挑战检查暂时挂起时执行。 问题 Q-7b8910a8d5f6dc05 (未决)

Diagnostic Management 中的相互协作

该流程遵循 Diagnostic Management 的统一停用模式,类似地,该模式也用于 ara::diag::CommunicationControl([SWS_DM_00810])、ara::diag::DownloadService([SWS_DM_00793])、ara::diag::EcuResetRequest([SWS_DM_01017])或 ara::diag::Monitor([SWS_DM_01089];参见 AUTOSAR_AP_SWS_Diagnostics §7.3.4.1.2 “Monitors”)以控制诊断消息流。

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

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

Header-Datei#include "ara/diag/sovd_proximity_challenge.h"
Scopeclass ara::diag::SovdProximityChallenge
Exception-Sicherheitexception safe
Thread-Sicherheitnot thread-safe

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_DM_01495
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01495@rel:R25-11#bd66e061
Content hash
bd66e061
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01495
Status: valid/unmigrated Version: rel:R25-11#78ed89f3 Versionshistorie & Revisions (1 transition, 5 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_DM_01495@rel:R25-11#78ed89f3
Point-in-Time History:
Recorded Revisions (5):
  • R25-11rel:R25-11#633f6e8f2026-09-30
  • R22-11rel:R22-11#383da6b42026-10-14
  • R23-11rel:R23-11#5beaaf9d2026-10-14
  • R24-11rel:R24-11#15ac8e732026-10-14
  • R25-11rel:R25-11#78ed89f32026-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

函数 ValidateResponse [SWS_DM_01493] Upstream: RS_Diag_04262

virtual ara::core::Future< ProximityChallengeValidationResultType > ValidateResponse (ara::core::Span< const ara::core::Byte > proximity Response, const MetaInfo &metaInfo) noexcept=0;

This function validates the proximity response sent by the client.

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

纯虚方法 ara::diag::SovdProximityChallenge::ValidateResponse 用于验证客户端传输的邻近度响应 [SWS_DM_01493]。一旦 SOVD 请求体包含属性 proximity_response [SWS_DM_01395](例如在终止操作执行的请求中 [SWS_DM_01391]),Diagnostic Server 实例就会调用此方法。传递的参数包括字节范围(byte-span)proximityResponse 以及上下文对象 metaInfo [SWS_DM_01493]。后者允许应用程序在需要时执行特定于客户端或特定于操作的检查 SWS Diagnostics 第215页。验证结果通过 ara::core::Future<ProximityChallengeValidationResultType> 异步提供 [SWS_DM_01493]。

该接口被声明为 noexcept 且异常安全(exception safe)[SWS_DM_01493]。未预先指定标准化的错误代码 [SWS_DM_01493]。Interpretation:邻近度验证失败可能会通过返回类型 ProximityChallengeValidationResultType 或 Future 的错误通道来表示。 问题 Q-1be6378537b59f2b (未决)

在并发性方面,线程安全性是有条件的(conditional):实现是否必须是线程安全的,取决于构造函数中确定的 ConcurrencyType [SWS_DM_01493]。缓冲区 proximityResponse 中传递的数据保持有效,直到关联的 Promise 被满足,或者处理被 CancellationHandler 取消 [SWS_DM_01493]。

该函数与通过 GetChallenge 提供 Challenge 协同工作 [SWS_DM_01398]。仅在成功验证邻近度响应后,服务器才会执行请求的操作,例如在 SovdOperationExecution 上通过 Terminate 终止操作 [SWS_DM_02179]。

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

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

Header-Datei#include "ara/diag/sovd_proximity_challenge.h"
Scopeclass ara::diag::SovdProximityChallenge
Exception-Sicherheitexception safe
Thread-Sicherheitconditional whether the function has to be implemented thread safe or non-thread safe is determined by the ConcurrencyType given in the constructor

Parameter (in)

ParameterBeschreibung
proximityResponseThe proximity_response sent by the client. Lifetime: Valid until Promise is fulfilled or the processing is cancelled by the cancellationHandler.
metaInfoThe meta information of a diagnostic service port

Rückgabewert

TypBeschreibung
ara::core::Future<ProximityChallengeValidationResultType >Value if the response was valid

Fehler

FehlercodeBeschreibung
This function does not specify any standardized errors.

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

Record
AUTOSAR/AP/record/SWS_DM_01493
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01493@rel:R25-11#97a51b97
Content hash
97a51b97
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01493
Status: valid/unmigrated Version: rel:R25-11#c8545e8c Versionshistorie & Revisions (1 transition, 5 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_DM_01493@rel:R25-11#c8545e8c
Point-in-Time History:
Recorded Revisions (5):
  • R25-11rel:R25-11#11c34c312026-09-30
  • R22-11rel:R22-11#14b581282026-10-14
  • R23-11rel:R23-11#a50ba5712026-10-14
  • R24-11rel:R24-11#9ffa5bad2026-10-14
  • R25-11rel:R25-11#c8545e8c2026-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

函数 ~SovdProximityChallenge [SWS_DM_01479] Upstream: RS_Diag_04262

virtual ~SovdProximityChallenge () noexcept;

Destructor of SovdProximityChallenge.

Header-Datei#include "ara/diag/sovd_proximity_challenge.h"
Scopeclass ara::diag::SovdProximityChallenge
Exception-Sicherheitexception safe
Thread-Sicherheitnot thread-safe

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

Record
AUTOSAR/AP/record/SWS_DM_01479
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01479@rel:R25-11#e8a742e1
Content hash
e8a742e1
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01479
Status: valid/unmigrated Version: rel:R25-11#7dc968f0 Versionshistorie & Revisions (1 transition, 5 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_DM_01479@rel:R25-11#7dc968f0
Point-in-Time History:
Recorded Revisions (5):
  • R25-11rel:R25-11#4b95c1102026-09-30
  • R22-11rel:R22-11#07bbb26d2026-10-14
  • R23-11rel:R23-11#7269e7f42026-10-14
  • R24-11rel:R24-11#38df87c82026-10-14
  • R25-11rel:R25-11#7dc968f02026-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