DEENESPTFRRUARHIKOZHNL

类 apext::com::secoc::FVM

[SWS_CM_11287] Upstream: RS_CM_00801, RS_CM_00802, RS_CM_00803, RS_CM_00804

class FVM {...};

A freshness value management interface to be implemented by the OEM/stack vendor. To be used by the freshness value management library implementer either OEM or stack vendor. The class will have a single instance in the CM.

Header-Datei#include "apext/com/secoc/fvm.h"
Forwarding-Header#include "apext/com/com_fwd.h"
Scopenamespace apext::com::secoc

用户指南人工智能生成

为通信管理提供用于 SecOC 厂商特定新鲜度值管理的接口。
AI 生成 未审核 模型: gemini-3.8-flash-medium · 推理强度: medium · 温度: 不可控 · 提示词: e018cf5c19e4 来源 未决问题(1)
译自德文指南gemini-3.8-flash-low · 2026-10-13 · 德文原文

为通信管理提供用于 SecOC 厂商特定新鲜度值管理的接口。

该类用作由 OEM 或协议栈厂商实现的接口,用于在通信管理中为 SecOC 提供和管理新鲜度值 [SWS_CM_11287]。它在发送和接收安全报文时通过 GetTxFreshness() 和 GetRxFreshness() 为 ara::com 提供新鲜度值,并通过 SetVerificationStatus() 接收验证结果 [SWS_CM_11274] [SWS_CM_11276]。其生命周期完全作为单例由 ara::com 管理 [SWS_CM_11272]。

上下文

类 apext::com::secoc::FVM 定义了 AUTOSAR Adaptive 通信管理内 Freshness Value Management (FVM) 的标准化接口 [SWS_CM_11287]。它充当扩展点(插件接口),由 OEM 或协议栈厂商实现,以便为精确到报文的安全保护提供特定于应用程序的新鲜度值 AUTOSAR_AP_SWS_CommunicationManagement §C.1.2 “Class: FVM”。交互方包括通信管理(ara::com)、密码学安全保护模块 SecOC 以及厂商的特定 FVM 库。

FVMKontext CM Communication Management (ara::com) FVM FVM-Schnittstelle (apext::com::secoc::FVM) CM->FVM steuert Lifecycle, fordert Frischewerte an LIB FVM-Implementierung (OEM / Stack Vendor) LIB->FVM implementiert

上下文图:通信管理与厂商特定新鲜度值库之间 FVM 接口的嵌入。来源:[SWS_CM_11272],[SWS_CM_11287],AUTOSAR_AP_SWS_CommunicationManagement §C.1.2 “Class: FVM”

生命周期

在通信管理内,仅存在该类的一个唯一实例 AUTOSAR_AP_SWS_CommunicationManagement §C.1.2 “Class: FVM”。SecOC-FreshnessValueManager 实现的整个生命周期完全由 ara::com 控制 [SWS_CM_11272]。FVM 实现的初始化强制通过调用方法 Initialize() 进行 [SWS_CM_11273] [SWS_CM_11290]。该接口的所有方法均声明为异常安全(noexcept)[SWS_CM_11288]。解释:由于实例化和生命周期管理由 ara::com 在内部执行,因此防止来自多个通信通道的并发调用的内部同步由具体的 FVM 插件实现负责。 问题 Q-02e8eaeef2145dbb (未决)

使用路径

在运行期间,通信管理区分安全报文的发送和接收:

  • 发送操作:当报文配置为进行 SecOC 传输并具有 freshnessValueId 时,通信管理将使用新鲜度值 ID 调用 GetTxFreshness() [SWS_CM_11274] [SWS_CM_11289]。成功返回后,该新鲜度值将在 FVContainer 中用于计算身份验证器(MAC),该计算在 E2E 保护计算之后进行 [SWS_CM_11274]。
  • 接收操作:如果传入报文的验证未被配置绕过 [SWS_CM_11372],SecOC 会在 E2E 检查之前调用 GetRxFreshness() [SWS_CM_11276] [SWS_CM_11288]。在此过程中,将传递 SecOCFreshnessValueID、接收到的截断新鲜度值(SecOCTruncatedFreshnessValue)以及先前的验证尝试次数(SecOCAuthVerifyAttempts)[SWS_CM_11288]。在对计算出的身份验证器进行比对后,通信管理通过 SetVerificationStatus() 并指定 VerificationStatus 向 FVM 报告结果 [SWS_CM_19999] [SWS_CM_11378]。
接收 SecOC 保护的消息时的验证流程ara::com (SecOC)apext::com::secoc::FVMGetRxFreshness(ID, TruncatedFV, Attempts)Result<FVContainer>计算并验证 MACSetVerificationStatus(ID, Status)Result<void>

时序图:接收安全报文时的验证流程,包括新鲜度值查询和状态反馈。来源:[SWS_CM_11276],[SWS_CM_11288],[SWS_CM_19999],AUTOSAR_AP_SWS_CommunicationManagement §8.1 “SecOC secure channel reception”

错误场景

错误通过 ara::core::Result 类型的返回类型进行指示:

  • 初始化错误:如果 FVM 实现的准备工作失败,Initialize() 将返回错误代码 ComSecOcFvmErrc::kFVInitializeFailed [SWS_CM_11290]。
  • 新鲜度值不可用:如果暂时无法确定发送或接收新鲜度值,GetTxFreshness() 和 GetRxFreshness() 将返回错误 ComSecOcFvmErrc::kFVNotAvailable [SWS_CM_11288] [SWS_CM_11289]。
  • 发送时的重试尝试:如果 GetTxFreshness() 返回可恢复错误 kFVNotAvailable 或身份验证器计算失败,系统将递增 Authentication Build Counter [SWS_CM_11275]。对报文的安全保护将以厂商特定方式重试;如果计数器达到配置的限制 SecOCAuthenticationBuildAttempts,则丢弃该报文 [SWS_CM_11275] AUTOSAR_AP_SWS_CommunicationManagement §8.1 “SecOC secure message build attempts”。
  • 验证失败时的状态消息:通过 SetVerificationStatus() 向 FVM 报告特定错误模式,例如 kSecOcVerificationFailure、kSecOcFreshnessFailure 或 kSecOcAuthenticationBuildFailure [SWS_CM_19999] [SWS_CM_11378]。

本类指南基于 AUTOSAR Adaptive R25-11 规范,并自动生成。

成员图

类图

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

G napext__com__secoc__FVM451 FVM + GetRxFreshness() + GetTxFreshness() + Initialize() + SetVerificationStatus()

详细视图

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

方法

Used by the SecOC to obtain the current freshness value.

ara::core::Result< FVContainer > GetRxFreshness (std::uint16_t Sec OCFreshnessValueID, const FVContainer &SecOCTruncatedFreshnessValue, std::uint16_t SecOCAuthVerifyAttempts) noexcept;

Used by the SecOC to obtain the current freshness value

ara::core::Result< FVContainer > GetTxFreshness (std::uint16_t Sec OCFreshnessValueID) noexcept;
Initialize 函数

Initializes FVM plugin implementation

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

This method is used by the SecOC to report all verification statuses to the Freshness Value Manager.

ara::core::Result< void > SetVerificationStatus (std::uint16_t sec OCFreshnessValueID, VerificationStatus secOCVerificationStatus) noexcept;

枚举

Defines the status of a verification

enum class VerificationStatus : std::uint8_t {...};

方法文档

函数 GetRxFreshness [SWS_CM_11288] Upstream: RS_CM_00801, RS_CM_00802, RS_CM_00803, RS_CM_00804

ara::core::Result< FVContainer > GetRxFreshness (std::uint16_t Sec OCFreshnessValueID, const FVContainer &SecOCTruncatedFreshnessValue, std::uint16_t SecOCAuthVerifyAttempts) noexcept;

Used by the SecOC to obtain the current freshness value.

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

成员函数 apext::com::secoc::FVM::GetRxFreshness 供SecOC层用于确定接收消息的完整新鲜度值 [SWS_CM_11288]。作为输入参数,该函数需要标识符 SecOCFreshnessValueID、根据 [SWS_CM_11286] 从安全消息中提取的 FVContainer 中的截短新鲜度值,以及计数器 SecOCAuthVerifyAttempts [SWS_CM_11288]。此计数器在首次验证尝试时以值 0 开始,并在同一消息后续每次尝试失败时递增 [SWS_CM_11288]。

该方法被指定为 noexcept 且异常安全(AUTOSAR_AP_SWS_CommunicationManagement §C.1.2.2.1.1 “GetRxFreshness”)。通过直接返回 ara::core::Result<FVContainer> 而不使用Future类型,该调用推测以同步阻塞方式进行处理。 问题 Q-2609cb9ffeb0d41d (未决)在成功的情况下,结果包含用于后续认证器(Authenticator)的MAC验证的完整新鲜度值 [SWS_CM_11288]。如果无法提供该值,该函数将返回可恢复的错误码 ComSecOcFvmErrc::kFVNotAvailable [SWS_CM_11288]。

新鲜度值确定是SecOC接收路径不可或缺的一部分:消息认证原则上在下游的E2E校验之前进行 [SWS_CM_11276],并与认证尝试计数器关联 [SWS_CM_11277]。标准中未定义关于可重入性或线程安全的具体要求;因此,并发调用时的行为推测取决于Freshness Value Manager的具体实现。 问题 Q-071e92f80c6e44db (未决)

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

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

Header-Datei#include "apext/com/secoc/fvm.h"
Scopeclass apext::com::secoc::FVM
Exception-Sicherheitexception safe

Template-Parameter

ParameterBeschreibung
FVContainerAs per [SWS_CM_11286]

Parameter (in)

ParameterBeschreibung
SecOCFreshnessValueIDSecOCTruncatedFreshnessValueSecOCAuthVerifyAttemptsthe identifier of the freshness value. the apext::com::secoc::FVContainer with the values from the received Secured I-PDU/ message the number of authentication verify attempts of this I-PDU/message since the last reception. The value is 0 for the first attempt and incremented on every unsuccessful verification attempt.

Rückgabewert

TypBeschreibung
ara::core::Result<FVContainer >• If successful: an ara::core::Result containing a ara:: core::Result::value_type containing a apext::com:: secoc::FVContainer that holds the freshness value to be used for the calculation of the authenticator by the SecOC or recoverable error. • If unsuccessful: an ara::core::Result containing an ara:: core::Result::error_type i.e. a corresponding ara:: com::ComErrc

Fehler

FehlercodeBeschreibung
ComSecOcFvmErrc::kFVNotAvailablerollback_semantics Freshness Value not available

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

Record
AUTOSAR/AP/record/SWS_CM_11288
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_11288@rel:R25-11#2dbfa7a2
Content hash
2dbfa7a2
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_11288
Status: valid/unmigrated Version: rel:R25-11#6d652806 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_CM_11288@rel:R25-11#6d652806
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#ce9299c32026-09-30
  • R20-11rel:R20-11#2d3cd3ce2026-10-14
  • R21-11rel:R21-11#2d3cd3ce2026-10-14
  • R22-11rel:R22-11#93c431962026-10-14
  • R23-11rel:R23-11#c565fe5b2026-10-14
  • R24-11rel:R24-11#13a0e3ec2026-10-14
  • R25-11rel:R25-11#6d6528062026-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

函数 GetTxFreshness [SWS_CM_11289] Upstream: RS_CM_00801, RS_CM_00802, RS_CM_00803, RS_CM_00804

ara::core::Result< FVContainer > GetTxFreshness (std::uint16_t Sec OCFreshnessValueID) noexcept;

Used by the SecOC to obtain the current freshness value

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

同步库函数 apext::com::secoc::FVM::GetTxFreshness([SWS_CM_11289])供SecOC处理使用,用于在通过Communication Management发送安全报文时获取当前新鲜度值([SWS_CM_11274],AUTOSAR_AP_SWS_CommunicationManagement 第224页 “SecOC secure channel sending”)。

用法与调用上下文

若在配置中为相应的服务接口元素指定了 freshnessValueId,则由 ara::com 进行调用([SWS_CM_11274]):

  • 参数:SecOCFreshnessValueID(类型 std::uint16_t)标识要请求的新鲜度值([SWS_CM_11289])。
  • 返回值:一个 ara::core::Result<FVContainer>([SWS_CM_11289])。在成功的情况下,其包含一个 apext::com::secoc::FVContainer([SWS_CM_11286]),该新鲜度值用于后续的认证器或MAC计算([SWS_CM_11274])。
  • 异常安全性:该函数被声明为 noexcept([SWS_CM_11289])。

错误处理与边界条件

如果无法提供有效的新鲜度值,该函数将返回带有错误码 ComSecOcFvmErrc::kFVNotAvailable(“Freshness Value not available”)的 ara::core::Result,并具有回滚语义([SWS_CM_11289])。在Adaptive标准中,未为此接口定义发往DET或DEM的特定报告。

流程与并发性

在发送过程中,该调用遵循严格的顺序([SWS_CM_11274]):

  1. 在此之前,必须已通过 ara::com 管理Freshness Value Manager的生命周期([SWS_CM_11272]),并且该实例必须已通过 apext::com::secoc::FVM::Initialize 初始化([SWS_CM_11273])。
  2. 在发送时,GetTxFreshness 在E2E保护计算之后进行([SWS_CM_11274])。
  3. 随后进行MAC计算、可选的截短以及安全消息的组装([SWS_CM_11274])。

关于可重入性,规范未作说明;然而,如果并行通信流同时请求新鲜度值,FVM实现推测必须设计为线程安全或可重入的。 问题 Q-a1d3e04b91b6c24d (未决)

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

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

Header-Datei#include "apext/com/secoc/fvm.h"
Scopeclass apext::com::secoc::FVM
Exception-Sicherheitexception safe

Template-Parameter

ParameterBeschreibung
FVContainerAs per [SWS_CM_11286]

Parameter (in)

ParameterBeschreibung
SecOCFreshnessValueIDthe identifier of the freshness value.

Rückgabewert

TypBeschreibung
ara::core::Result<FVContainer >• If successful: an ara::core::Result containing a ara:: core::Result::value_type containing a apext::com:: secoc::FVContainer that holds the freshness value to be used for the calculation of the authenticator by the SecOC or recoverable error. • If unsuccessful: an ara::core::Result containing an ara:: core::Result::error_type i.e. a corresponding ara:: com::ComErrc

Fehler

FehlercodeBeschreibung
ComSecOcFvmErrc::kFVNotAvailablerollback_semantics Freshness Value not available

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

Record
AUTOSAR/AP/record/SWS_CM_11289
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_11289@rel:R25-11#d1e4ceda
Content hash
d1e4ceda
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_11289
Status: valid/unmigrated Version: rel:R25-11#65861fc2 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_CM_11289@rel:R25-11#65861fc2
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#5a33d7982026-09-30
  • R20-11rel:R20-11#edcd09152026-10-14
  • R21-11rel:R21-11#cd25fec42026-10-14
  • R22-11rel:R22-11#c50822302026-10-14
  • R23-11rel:R23-11#61be10642026-10-14
  • R24-11rel:R24-11#b538d6052026-10-14
  • R25-11rel:R25-11#65861fc22026-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

函数 Initialize [SWS_CM_11290] Upstream: RS_CM_00801, RS_CM_00802, RS_CM_00803, RS_CM_00804

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

Initializes FVM plugin implementation

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

用法与调用上下文

作用域 apext::com::secoc::FVM 内的同步库函数 Initialize 用于初始化Freshness Value Manager(FVM)的厂商特定插件实现,以用于通过SecOC进行的安全相关通信 [SWS_CM_11290]。该声明可通过头文件 apext/com/secoc/fvm.h 获取 SWS CommunicationManagement §C.1.2.2.1.3 “Initialize”。

该函数不接受任何参数,并声明了异常安全性 noexcept(exception safe)[SWS_CM_11290]。FVM的生命周期管理强制由通信中间件 ara::com 承担 [SWS_CM_11272],该中间件通过显式调用此接口来执行FVM插件的初始化 [SWS_CM_11273]。Interpretation:对于应用程序开发者而言,不存在直接调用的上下文,因为它是作为平台的插件提供的,且控制权完全在 ara::com。 问题 Q-5b5c8b1a42c3bd3a (未决)

错误处理

操作的结果通过返回类型 ara::core::Result<void> 进行传达 [SWS_CM_11290]:

  • 成功:初始化成功时,ara::core::Result 包含一个空值(value_type 为 void)[SWS_CM_11290]。
  • 初始化失败:如果Freshness Value Manager未能初始化,将返回一个带有特定错误码 ComSecOcFvmErrc::kFVInitializeFailed 的错误对象;此时回滚语义生效以保持已定义的状态 [SWS_CM_11290]。

交互与顺序

使用 Initialize 进行初始化构成了系统中所有其他FVM服务的功能先决条件 [SWS_CM_11273]。只有在成功执行之后,在SecOC发送操作中且在E2E计算之后,ara::com 才允许访问接口 apext::com::secoc::FVM::GetTxFreshness,以检索已配置的 freshnessValueId 属性的时效性值 [SWS_CM_11274]。

此使用说明由AI基于AUTOSAR Adaptive Platform R25-11规范整理而成。

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

Header-Datei#include "apext/com/secoc/fvm.h"
Scopeclass apext::com::secoc::FVM
Exception-Sicherheitexception safe

Rückgabewert

TypBeschreibung
ara::core::Result< void >• If successful: an ara::core::Result containing a ara:: core::Result::value_type containing a void • If unsuccessful: an ara::core::Result containing an ara:: core::Result::error_type i.e. a corresponding ara:: com::ComErrc

Fehler

FehlercodeBeschreibung
ComSecOcFvmErrc::kFVInitializeFailedrollback_semantics Initialization of Freshness Value Manager failed

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

Record
AUTOSAR/AP/record/SWS_CM_11290
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_11290@rel:R25-11#edb860f8
Content hash
edb860f8
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_11290
Status: valid/unmigrated Version: rel:R25-11#11a4e44b 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_CM_11290@rel:R25-11#11a4e44b
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#322a9af72026-09-30
  • R20-11rel:R20-11#3d48fa7f2026-10-14
  • R21-11rel:R21-11#3d48fa7f2026-10-14
  • R22-11rel:R22-11#b6c4832f2026-10-14
  • R23-11rel:R23-11#d9a72c7b2026-10-14
  • R24-11rel:R24-11#dd5117f72026-10-14
  • R25-11rel:R25-11#11a4e44b2026-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

函数 SetVerificationStatus [SWS_CM_19999] Upstream: RS_CM_00801, RS_CM_00802, RS_CM_00803, RS_CM_00804

ara::core::Result< void > SetVerificationStatus (std::uint16_t sec OCFreshnessValueID, VerificationStatus secOCVerificationStatus) noexcept;

This method is used by the SecOC to report all verification statuses to the Freshness Value Manager.

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

使用

同步方法 apext::com::secoc::FVM::SetVerificationStatus 由 SecOC 调用,以向 Freshness Value Manager (FVM) 报告校验结果 [SWS_CM_19999]。它通过头文件 apext/com/secoc/fvm.h 声明,并需要两个参数 AUTOSAR_AP_SWS_CommunicationManagement §C.1.2.2.1.4 “SetVerificationStatus”:

  • secOCFreshnessValueID (std::uint16_t):新鲜度值的唯一标识符。
  • secOCVerificationStatus (VerificationStatus):指定标识符的校验结果。

错误处理与并发

该函数声明为 noexcept 并被视为异常安全(exception safe)[SWS_CM_19999]。返回类型 ara::core::Result<void> 通过空结果指示成功执行。在发生错误时,Result 对象包含一个 ara::com::ComErrc 类型的错误码,尽管规范未定义任何特定的标准化错误码 [SWS_CM_19999]。

交互与状态

该函数在管理新鲜度值时将 SecOC 与 FVM 关联起来。它的状态为 DRAFT AUTOSAR_AP_SWS_CommunicationManagement §C.1.2.2.1.4 “SetVerificationStatus”。解释:传递的状态信息大概率会被 FVM 在内部用于跟踪新鲜度值的同步状态或计数值。 问题 Q-156ad8f991c99b7d (未决)

本使用说明由自动化生成,完全基于 Release R25-11 的规范。

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

Header-Datei#include "apext/com/secoc/fvm.h"
Scopeclass apext::com::secoc::FVM
Exception-Sicherheitexception safe

Parameter (in)

ParameterBeschreibung
secOCFreshnessValueIDthe identifier of the freshness value.
secOCVerificationStatusverification status result for the given FreshnessValueID

Rückgabewert

TypBeschreibung
ara::core::Result< void >• If successful: an ara::core::Result containing a ara:: core::Result::value_type containing a void • If unsuccessful: an ara::core::Result containing an ara:: core::Result::error_type i.e. a corresponding ara:: com::ComErrc

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_CM_19999
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_19999@rel:R25-11#63dd5bda
Content hash
63dd5bda
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_19999
Status: valid/unmigrated Version: rel:R25-11#4590caf9 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_19999@rel:R25-11#4590caf9
Point-in-Time History:
Recorded Revisions (3):
  • R25-11rel:R25-11#be8322432026-09-30
  • R24-11rel:R24-11#feb309092026-10-14
  • R25-11rel:R25-11#4590caf92026-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

枚举文档

枚举 VerificationStatus [SWS_CM_11378] Upstream: RS_CM_00801, RS_CM_00802, RS_CM_00803, RS_CM_00804

enum class VerificationStatus :               std::uint8_t {...};

Defines the status of a verification

Header-Datei#include "apext/com/secoc/fvm.h"
Forwarding-Header#include "apext/com/com_fwd.h"
Scopeclass apext::com::secoc::FVM
SymbolVerificationStatus
Basistypstd::uint8_t

Werte

EnumeratorBeschreibung
SuccessVerification successful
kSecOcVerificationFailure= 0x01 Verification not successful
kSecOcFreshnessFailure= 0x02 Verification not successful because of wrong freshness value
kSecOcAuthenticationBuildFailure= 0x03 Verification not successful because of wrong build authentication codes
kSecOcNoVerification= 0x04 Verification has been skipped and the data has been provided to the application as is
kSecOcVerificationFailureOverwritten= 0x05 Verification failed, but the PDU was passed on to the application due to the override status for this PDU

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

Record
AUTOSAR/AP/record/SWS_CM_11378
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_CM_11378@rel:R25-11#08f36cf0
Content hash
08f36cf0
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_11378
Status: valid/unmigrated Version: rel:R25-11#7e9db4a6 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_11378@rel:R25-11#7e9db4a6
Point-in-Time History:
Recorded Revisions (3):
  • R25-11rel:R25-11#b0fa1d442026-09-30
  • R24-11rel:R24-11#23fd47892026-10-14
  • R25-11rel:R25-11#7e9db4a62026-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