枚举 ComE2EErrc [SWS_CM_10474] Upstream: RS_AP_00130
enum class ComE2EErrc : ara::core::ErrorDomain::CodeType {...};
Defines the error codes for the ara::com::e2e::ComE2EErrc
| Header-Datei | #include "ara/com/e2e/e2e_error_domain.h" |
|---|---|
| Forwarding-Header | #include "ara/com/com_fwd.h" |
| Scope | namespace ara::com::e2e |
| Symbol | ComE2EErrc |
| Basistyp | ara::core::ErrorDomain::CodeType |
Werte
| Enumerator | Beschreibung |
|---|---|
| kRepeated | =1 Data has a repeated counter |
| kWrongSequence | =2 The checks of the Data in this cycle were successful, with the exception of counter jump, which changed more than the allowed delta |
| kError | =3 Error not related to counters occurred (e.g. wrong crc, wrong length, wrong Data ID) or the return of the check function was not OK |
| kNoNewData | =5 No new data is available |
| kUnspecifiedE2EError | = 13 A remote service returned an unspecified E2E error. |
枚举 ComE2EErrc 在命名空间 ara::com::e2e 中基于 ara::core::ErrorDomain::CodeType [SWS_CM_10474] 定义了端到端保护(E2E)的特定错误码。在错误域 ara::com::e2e::ComE2EErrorDomain 内,该类型通过类型别名 Errc 提供 [SWS_CM_12504]。
枚举器值描述了确定的校验结果和错误状态 [SWS_CM_10474]:
kRepeated:数据呈现出重复的计数值 [SWS_CM_10474]。kWrongSequence:校验成功,但计数跳变超过了允许的增量 [SWS_CM_10474]。kError:发生了与计数器无关的错误(例如错误的CRC、错误的长度或无效的Data-ID),或者校验函数的返回结果不正常 [SWS_CM_10474]。kNoNewData:没有新数据可用 [SWS_CM_10474]。kUnspecifiedE2EError:远端服务返回了未指定的E2E错误 [SWS_CM_10474]。
在服务端请求处理中,当消息的E2E校验失败时,ComE2EErrc 将作为参数 errorCode 传递给骨架的方法 E2EErrorHandler [SWS_CM_10470],AUTOSAR_AP_SWS_CommunicationManagement §7.4.1.2.3.3 “E2E error notification”。如果没有新的请求消息就绪,则必须使用 ComE2EErrc::kNoNewData 以及 dataID = 0 和 messageCounter = 0 调用处理程序 [SWS_CM_00047]。在错误处理程序执行完毕后,将进行响应消息的E2E保护 [SWS_CM_90481]。
关于并发性和边界条件:方法 E2EErrorHandler 未被指定为可重入,且不是 exception safe [SWS_CM_10470]。其注册完全在运行时之前静态进行;不提供动态注册或注销 AUTOSAR_AP_SWS_CommunicationManagement §7.4.1.2.3.3 “E2E error notification”。此外,在发生CRC错误时,服务端应用程序不得依赖传入的Data-ID,因为该标识符可能已损坏 [SWS_CM_10470]。
本文字由 AI 创建,且完全基于版本 R25-11 的规范。
实现者指南即将推出(复杂度 I2)
Request a governed re-review of this record. The record is not changed immediately.
- Record
AUTOSAR/AP/record/SWS_CM_10474- Status
- valid/unmigrated
- Version
AUTOSAR/AP/record/SWS_CM_10474@rel:R25-11#64c070af- Content hash
64c070af- Source
- https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_CommunicationManagement.pdf#nameddest=SWS_CM_10474
Status: valid/unmigrated
Version: rel:R25-11#badd908e
Versionshistorie & Revisions (1 transition, 8 revision)
- Current State
valid/unmigrated- Reason
- mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
- Campaign
2026-08-13-status-backfill- Active Version
AUTOSAR/AP/record/SWS_CM_10474@rel:R25-11#badd908e
Recorded Revisions (8):
- R25-11
rel:R25-11#7fdc69172026-09-30 - R19-11
rel:R19-11#6a4cea2f2026-10-14 - R20-11
rel:R20-11#61179def2026-10-14 - R21-11
rel:R21-11#61179def2026-10-14 - R22-11
rel:R22-11#cd4dc4512026-10-14 - R23-11
rel:R23-11#9b21e5562026-10-14 - R24-11
rel:R24-11#e3693bd52026-10-14 - R25-11
rel:R25-11#badd908e2026-10-14 active
Requirement Text as-of this release:
Curation Decisions:
Reachable Artifacts & Dependents:
| Date | Actor | Transition | Reason / Rationale | Campaign |
|---|---|---|---|---|
| 2026-08-13 | tool | none → valid/unmigrated | mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record | 2026-08-13-status-backfill |
gemini-3.8-flash-low· 2026-10-13 · 德文原文