DEENESPTFRRUARHIKOZHNL

类 apext::diag::uds_transport::UdsMessage

[SWS_DM_00291] Upstream: RS_Diag_04147

class UdsMessage {...};

class represents an UDS message exchanged between DM generic core (UdsTransport ProtocolMgr) and a specific implementation of UdsTransportProtocolHandler on diagnostic request reception path or diagnostic response transmission path. UdsMessage provides the storage for UDS requests/responses.

Instances of UdsMessage (with optimized resource allocation) are only created by DM generic core, the UdsTransportProtocolHandler can read/write on it.

Header-Datei#include "apext/diag/uds_transport/uds_message.h"
Forwarding-Header#include "apext/diag/diag_fwd.h"
Scopenamespace apext::diag::uds_transport

用户指南人工智能生成

在 Adaptive 诊断管理器中进行数据交换时用作 UDS 消息的存储和信息载体。
AI 生成 未审核 模型: gemini-3.8-flash-medium · 推理强度: medium · 温度: 不可控 · 提示词: b58e356aa414 来源 未决问题(1)
译自德文指南gemini-3.8-flash-low · 2026-10-13 · 德文原文

在 Adaptive 诊断管理器中进行数据交换时用作 UDS 消息的存储和信息载体。

类 apext::diag::uds_transport::UdsMessage 代表在通用诊断核心与传输特定 Handler 之间交换的诊断消息的标准化存储和传输对象。其实例仅由具有优化内存分配的通用核心创建,并通过 UdsMessagePtr 提供 [SWS_DM_09012]。在接收路径中,Handler 从服务 ID 开始填充提供的数据缓冲区,并在附加可能的通道元数据后转发该消息 [SWS_DM_00388]。如果核心因现有负载过高而无法处理消息,则拒绝分配并返回空指针 [SWS_DM_00386]。

上下文

类 apext::diag::uds_transport::UdsMessage 代表在 Diagnostic Management 通用核心(DM Generic Core 即 UdsTransportProtocolMgr)与 UdsTransportProtocolHandler 的特定实现之间交换的 UDS 消息的中心数据和存储对象。它用作传入 UDS 请求与传出 UDS 响应的封装和存储(Storage)。

除有效负载外,UdsMessage 还传输诊断通信的寻址参数:经由 GetSa() [SWS_DM_00297] 的源地址 Address [SWS_DM_00293]、经由 GetTa() [SWS_DM_00298] 的目标地址,以及经由 GetTaType() [SWS_DM_00299] 的地址类型 TargetAddressType(带有 kPhysical 的物理寻址或带有 kFunctional 的功能寻址)[SWS_DM_00296]。此外,还可以经由 AddMetaInfo() 附加通道特定的元信息,例如针对 DoIP 的连接参数 [SWS_DM_00294],[SWS_DM_00302]。

UdsMessageKontext mgr UdsTransportProtocolMgr (DM Generic Core) handler UdsTransportProtocolHandler (Transport-Plugin) mgr->handler 传递 UdsMessagePtr msg UdsMessage (apext::diag::uds_transport) mgr->msg erzeugt & reserviert handler->mgr leitet weiter via HandleMessage handler->msg 填充有效负载与 元数据

上下文图:DM 核心、传输 Handler 与 UdsMessage 之间的相互作用。来源:[SWS_DM_09012]、[SWS_DM_00385]、[SWS_DM_00345]

生命周期

UdsMessage 的实例通过优化的资源分配仅由 Diagnostic Management 的通用核心创建。为了防止协议 Handler 进行不受控的实例化,默认构造函数被声明为受保护的(protected)[SWS_DM_09012]。Handler 仅通过类型为 apext::diag::uds_transport::UdsMessagePtr [SWS_DM_00303] 的所有权指针获取对消息对象的访问权,或者对于纯只读访问,通过 apext::diag::uds_transport::UdsMessageConstPtr [SWS_DM_00304],AUTOSAR_AP_SWS_Diagnostics 第98页 获取。

对象的销毁通过虚析构函数 ~UdsMessage() [SWS_DM_09010] 进行。关于并发性,用于地址信息的查询方法(GetSa、GetTa、GetTaType)是可重入的(reentrant)且异常安全的(noexcept)[SWS_DM_00297],[SWS_DM_00298],[SWS_DM_00299]。相反,通过 GetPayload() 访问数据缓冲区以及通过 AddMetaInfo() 添加元数据被归类为非线程安全,因为实现在这些调用期间允许执行缓冲区与资源分配 [SWS_DM_00300],[SWS_DM_00301],[SWS_DM_00302]。

使用路径

在接收路径的常规流程中,UdsTransportProtocolHandler 通过 UdsTransportProtocolMgr::IndicateMessage() 向 DM 通告传入的 UDS 请求 [SWS_DM_00385]。如果 DM 准备好接收,它将以状态 kIndicationOk 进行确认,并传递一个最小大小为 1 个字节且具有 DM 所需缓冲区容量的 UdsMessagePtr [SWS_DM_00385]。

随后,协议 Handler 调用非常量方法 GetPayload(),以获取对基础存储区(uds_transport::ByteSpan&)的可写引用 [SWS_DM_00301]。它从服务标识符(SID)开始填充此缓冲区,直到达到 UdsMessage 对象的最大容量或完整消息长度 [SWS_DM_00388]。在可选地经由 AddMetaInfo() [SWS_DM_00302] 补充通道特定元数据后,Handler 通过 UdsTransportProtocolMgr::HandleMessage() 将填充后的对象转发给诊断核心 [SWS_DM_00345]。(解释:在诊断响应的传输路径中,UdsMessage 的提供可能类似地由通用核心执行。) 问题 Q-4f568a0e527bdfbc (未决)

接收路径中的消息处理流程HandlerManagerUdsMessageIndicateMessage(sa, ta, taType, ...)altDM bereit (kIndicationOk)std::pair(kIndicationOk, UdsMessagePtr)GetPayload()uds_transport::ByteSpan&从 SID 开始填充有效负载AddMetaInfo(metaInfo)HandleMessage(udsMessagePtr)DM ausgelastet (kIndicationOccupied)std::pair(kIndicationOccupied, nullptr)Nachricht verworfen

时序图:接收 UDS 消息时的交互序列。来源:[SWS_DM_00385]、[SWS_DM_00386]、[SWS_DM_00388]、[SWS_DM_00301]、[SWS_DM_00302]、[SWS_DM_00345]

错误场景

如果 DM 无法处理通过 IndicateMessage() 通告的消息(因为其正忙于主动处理同一 Tester-Present 会话的服务),它将返回状态 kIndicationOccupied 以及等于 nullptr 的 UdsMessagePtr [SWS_DM_00386]。在这种情况下,不提供 UdsMessage 并中止接收。同样,未知的目标地址会导致结果 kIndicationUnknownTargetAddress,且消息引用为空指针 AUTOSAR_AP_SWS_Diagnostics 第100页。

填充缓冲区时,协议 Handler 必须注意指定的缓冲区容量:超出 UdsMessage 所提供容量的传入请求将被截断至完整缓冲区大小 [SWS_DM_00388]。此外,从多个线程对 GetPayload() 或 AddMetaInfo() 进行并发、无保护的访问会导致未定义行为,因为这些接口被明确指定为非线程安全(unsafe)[SWS_DM_00300],[SWS_DM_00301],[SWS_DM_00302]。

本类指南基于针对 Adaptive Platform 的 AUTOSAR 规范 R25-11 编写。

成员图

类图

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

G napext__diag__uds_transport__UdsMessage883 UdsMessage + ~UdsMessage() + AddMetaInfo() + GetPayload() + GetSa() + GetTa() + GetTaType() + UdsMessage()

详细视图

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

构造函数和析构函数

UdsMessage 函数

non public default constructor. The default constructor is protected as we want to forbid, that UdsTransportProtocolHandlers do create UdsMessages on its own! Only DM is allowed to create and hands over UdsMessagePtrs to UdsTransportProtocolHandler.

UdsMessage () noexcept;

Destructing the uds message.

virtual ~UdsMessage () noexcept=default;

方法

add new metaInfo to this message.

virtual void AddMetaInfo (MetaInfoMap metaInfo) noexcept;
GetPayload 函数 2

Get the UDS message data starting with the SID (A_Data as per ISO) with no write access.

重载 GetPayload 2
virtual const ara::core::Vector< const std::uint8_t > & GetPayload () const noexcept; SWS_DM_00300
virtual uds_transport::ByteSpan & GetPayload () noexcept; SWS_DM_00301
GetSa 函数

Get the source address of the uds message.

virtual Address GetSa () const noexcept;
GetTa 函数

Get the target address of the uds message.

virtual Address GetTa () const noexcept;
GetTaType 函数

Get the target address type (phys/func) of the uds message.

virtual TargetAddressType GetTaType () const noexcept;

类型别名

Address 类型别名

Type for UDS source and target addresses.

using Address = std::uint16_t;
MetaInfoMap 类型别名

Type for the meta information attached to a UdsMessage.

枚举

type of target address in UdsMessage

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

方法文档

函数 AddMetaInfo [SWS_DM_00302] Upstream: RS_Diag_04147, RS_Diag_04170

virtual void AddMetaInfo (MetaInfoMap metaInfo) noexcept;

add new metaInfo to this message.

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

类 apext::diag::uds_transport::UdsMessage 的虚成员函数 AddMetaInfo 用于为诊断报文分配新的元数据 [SWS_DM_00302]。它通常由传输协议插件调用,以向相应的诊断请求附加通道特定附加信息——例如针对 DoIP 的预定义元数据键 AUTOSAR_AP_SWS_Diagnostics §C.5.2.2.2.1 “AddMetaInfo”。

使用该接口适用以下框架条件 [SWS_DM_00302]:

  • 调用上下文与头文件:声明通过头文件 apext/diag/uds_transport/uds_message.h 提供,并直接在 UdsMessage 的实例上执行 AUTOSAR_AP_SWS_Diagnostics §C.5.2.2.2.1 “AddMetaInfo”。
  • 形参:类型为 MetaInfoMap 的输入参数 metaInfo 传递请求待添加的元信息 [SWS_DM_00302]。
  • 返回值:该同步函数无返回值(void)[SWS_DM_00302]。
  • 错误处理:该操作带有标识符 noexcept,并被指定为异常安全(exception safe);不存在特定的错误代码 [SWS_DM_00302]。

关于并发性,该方法被声明为非线程安全(thread safety: unsafe)[SWS_DM_00302]。解释:调用方因此可能负责通过外部机制保护对 UdsMessage 的同一实例的并发访问,因为规范未提供内部同步 AUTOSAR_AP_SWS_Diagnostics §C.5.2.2.2.1 “AddMetaInfo”。 问题 Q-c2de8aa28c94aed8 (未决)

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

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

Header-Datei#include "apext/diag/uds_transport/uds_message.h"
Scopeclass apext::diag::uds_transport::UdsMessage
Exception-Sicherheitexception safe
Thread-Sicherheitunsafe

Parameter (in)

ParameterBeschreibung
metaInfoMetaInfo of the request.

Rückgabewert

TypBeschreibung
None
Hinweise: typically called by the Transport Protocol plugin to add channel specific meta-info. See further MetaInfo related SWS, there are already predefined meta-info keys for DoIP....)

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

Record
AUTOSAR/AP/record/SWS_DM_00302
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00302@rel:R25-11#b3f9fa14
Content hash
b3f9fa14
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00302
Status: valid/unmigrated Version: rel:R25-11#675a6873 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_DM_00302@rel:R25-11#675a6873
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#5d66ee092026-09-30
  • R19-11rel:R19-11#59de85012026-10-14
  • R20-11rel:R20-11#fc0f4e762026-10-14
  • R21-11rel:R21-11#f7ca4f0c2026-10-14
  • R22-11rel:R22-11#fe9effec2026-10-14
  • R23-11rel:R23-11#ff73c0922026-10-14
  • R24-11rel:R24-11#f6433d2e2026-10-14
  • R25-11rel:R25-11#675a68732026-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

函数 GetPayload [SWS_DM_00300] Upstream: RS_Diag_04147

virtual const ara::core::Vector< const std::uint8_t > & GetPayload () const noexcept;

Get the UDS message data starting with the SID (A_Data as per ISO) with no write access.

Header-Datei#include "apext/diag/uds_transport/uds_message.h"
Scopeclass apext::diag::uds_transport::UdsMessage
Exception-Sicherheitexception safe
Thread-Sicherheitunsafe

Rückgabewert

TypBeschreibung
const ara::core::Vector<const std::uint8_t > &The entire payload (A_Data) with no write access.
Hinweise: Marked as "unsafe" with regard to thread-safety, as the implementation is allowed to do a ressource allocation of buffer in the context of this call.

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

Record
AUTOSAR/AP/record/SWS_DM_00300
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00300@rel:R25-11#5e63ccb9
Content hash
5e63ccb9
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00300
Status: valid/unmigrated Version: rel:R25-11#cf123c75 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_DM_00300@rel:R25-11#cf123c75
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#09c8a7132026-09-30
  • R19-11rel:R19-11#393107622026-10-14
  • R20-11rel:R20-11#6dc0e2a42026-10-14
  • R21-11rel:R21-11#6dc0e2a42026-10-14
  • R22-11rel:R22-11#8c7f7b792026-10-14
  • R23-11rel:R23-11#8a0928b62026-10-14
  • R24-11rel:R24-11#a212c0af2026-10-14
  • R25-11rel:R25-11#cf123c752026-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

函数 GetPayload [SWS_DM_00301] Upstream: RS_Diag_04147

virtual uds_transport::ByteSpan & GetPayload () noexcept;

Return the underlying buffer for write access.

Header-Datei#include "apext/diag/uds_transport/uds_message.h"
Scopeclass apext::diag::uds_transport::UdsMessage
Exception-Sicherheitexception safe
Thread-Sicherheitunsafe

Rückgabewert

TypBeschreibung
uds_transport::ByteSpan&payload of the UDSMessage starting from SID.
Hinweise: Needed by UdsTransportProtocolHandler implementation to fill the UdsMessage with data in RX path. I.e. UdsTransportProtocolHandler implementation gets the UdsMessage instance from a call to UdsTransportProtocolMgr::IndicateMessage() and then calls this method on it and writes into the returned uds_transport::ByteVector. Marked as "unsafe" with regard to thread safety as implementation is allowed to do ressource allocation of buffer in the context of this call.

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

Record
AUTOSAR/AP/record/SWS_DM_00301
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00301@rel:R25-11#22892c8f
Content hash
22892c8f
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00301
Status: valid/unmigrated Version: rel:R25-11#7ee8d83d 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_DM_00301@rel:R25-11#7ee8d83d
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#ba7e789e2026-09-30
  • R19-11rel:R19-11#f9a613082026-10-14
  • R20-11rel:R20-11#eb7021ce2026-10-14
  • R21-11rel:R21-11#eb7021ce2026-10-14
  • R22-11rel:R22-11#003bb4d12026-10-14
  • R23-11rel:R23-11#8d6801992026-10-14
  • R24-11rel:R24-11#161f75542026-10-14
  • R25-11rel:R25-11#7ee8d83d2026-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

函数 GetSa [SWS_DM_00297] Upstream: RS_Diag_04147, RS_Diag_04174

virtual Address GetSa () const noexcept;

Get the source address of the uds message.

Header-Datei#include "apext/diag/uds_transport/uds_message.h"
Scopeclass apext::diag::uds_transport::UdsMessage
Exception-Sicherheitexception safe
Thread-Sicherheitreentrant

Rückgabewert

TypBeschreibung
AddressThe source address of the uds message.

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

Record
AUTOSAR/AP/record/SWS_DM_00297
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00297@rel:R25-11#5e6e84d4
Content hash
5e6e84d4
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00297
Status: valid/unmigrated Version: rel:R25-11#d7bb6b79 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_DM_00297@rel:R25-11#d7bb6b79
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#c34487032026-09-30
  • R19-11rel:R19-11#c0a476352026-10-14
  • R20-11rel:R20-11#12ec510d2026-10-14
  • R21-11rel:R21-11#0f7db1342026-10-14
  • R22-11rel:R22-11#77c3d0d52026-10-14
  • R23-11rel:R23-11#ff91c9542026-10-14
  • R24-11rel:R24-11#d7bb6b792026-10-14
  • R25-11rel:R25-11#d7bb6b792026-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

函数 GetTa [SWS_DM_00298] Upstream: RS_Diag_04147, RS_Diag_04174

virtual Address GetTa () const noexcept;

Get the target address of the uds message.

Header-Datei#include "apext/diag/uds_transport/uds_message.h"
Scopeclass apext::diag::uds_transport::UdsMessage
Exception-Sicherheitexception safe
Thread-Sicherheitreentrant

Rückgabewert

TypBeschreibung
AddressThe target address of the uds message.

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

Record
AUTOSAR/AP/record/SWS_DM_00298
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00298@rel:R25-11#15018eda
Content hash
15018eda
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00298
Status: valid/unmigrated Version: rel:R25-11#1968e933 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_DM_00298@rel:R25-11#1968e933
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#a57698b02026-09-30
  • R19-11rel:R19-11#222abc9b2026-10-14
  • R20-11rel:R20-11#47659dac2026-10-14
  • R21-11rel:R21-11#47659dac2026-10-14
  • R22-11rel:R22-11#4fd3e98b2026-10-14
  • R23-11rel:R23-11#fa73a0662026-10-14
  • R24-11rel:R24-11#1968e9332026-10-14
  • R25-11rel:R25-11#1968e9332026-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

函数 GetTaType [SWS_DM_00299] Upstream: RS_Diag_04147, RS_Diag_04174

virtual TargetAddressType GetTaType () const noexcept;

Get the target address type (phys/func) of the uds message.

Header-Datei#include "apext/diag/uds_transport/uds_message.h"
Scopeclass apext::diag::uds_transport::UdsMessage
Exception-Sicherheitexception safe
Thread-Sicherheitreentrant

Rückgabewert

TypBeschreibung
TargetAddressTypeThe target address type of the uds message.

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

Record
AUTOSAR/AP/record/SWS_DM_00299
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00299@rel:R25-11#1544c5d9
Content hash
1544c5d9
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00299
Status: valid/unmigrated Version: rel:R25-11#28674895 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_DM_00299@rel:R25-11#28674895
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#a70e61ea2026-09-30
  • R19-11rel:R19-11#1d0afa252026-10-14
  • R20-11rel:R20-11#7020b5872026-10-14
  • R21-11rel:R21-11#d76865812026-10-14
  • R22-11rel:R22-11#8c2a80882026-10-14
  • R23-11rel:R23-11#575d68862026-10-14
  • R24-11rel:R24-11#286748952026-10-14
  • R25-11rel:R25-11#286748952026-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

函数 UdsMessage [SWS_DM_09012] Upstream: RS_Diag_04147

UdsMessage () noexcept;

non public default constructor. The default constructor is protected as we want to forbid, that UdsTransportProtocolHandlers do create UdsMessages on its own! Only DM is allowed to create and hands over UdsMessagePtrs to UdsTransportProtocolHandler.

Header-Datei#include "apext/diag/uds_transport/uds_message.h"
Scopeclass apext::diag::uds_transport::UdsMessage
Exception-Sicherheitexception safe
Thread-Sicherheitnot thread-safe
Sichtbarkeitprotected

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

Record
AUTOSAR/AP/record/SWS_DM_09012
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_09012@rel:R25-11#bd317e45
Content hash
bd317e45
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_09012
Status: valid/unmigrated Version: rel:R25-11#c9baa661 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_DM_09012@rel:R25-11#c9baa661
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#78230a9a2026-09-30
  • R19-11rel:R19-11#73995c592026-10-14
  • R20-11rel:R20-11#0a39f1072026-10-14
  • R21-11rel:R21-11#0a39f1072026-10-14
  • R22-11rel:R22-11#46e811332026-10-14
  • R23-11rel:R23-11#294829f92026-10-14
  • R24-11rel:R24-11#44977ca32026-10-14
  • R25-11rel:R25-11#c9baa6612026-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

函数 ~UdsMessage [SWS_DM_09010] Upstream: RS_Diag_04147

virtual ~UdsMessage () noexcept=default;

Destructing the uds message.

Header-Datei#include "apext/diag/uds_transport/uds_message.h"
Scopeclass apext::diag::uds_transport::UdsMessage
Exception-Sicherheitexception safe

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

Record
AUTOSAR/AP/record/SWS_DM_09010
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_09010@rel:R25-11#aae1d564
Content hash
aae1d564
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_09010
Status: valid/unmigrated Version: rel:R25-11#3728f16c 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_DM_09010@rel:R25-11#3728f16c
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#878e531e2026-09-30
  • R19-11rel:R19-11#7da6ac4b2026-10-14
  • R20-11rel:R20-11#002db0a02026-10-14
  • R21-11rel:R21-11#002db0a02026-10-14
  • R22-11rel:R22-11#be5d0d222026-10-14
  • R23-11rel:R23-11#311ce6c92026-10-14
  • R24-11rel:R24-11#e1b3e27b2026-10-14
  • R25-11rel:R25-11#3728f16c2026-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

枚举文档

枚举 TargetAddressType [SWS_DM_00296] Upstream: RS_Diag_04147

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

type of target address in UdsMessage

Header-Datei#include "apext/diag/uds_transport/uds_message.h"
Forwarding-Header#include "apext/diag/diag_fwd.h"
Scopeclass apext::diag::uds_transport::UdsMessage
SymbolTargetAddressType
Basistypstd::uint8_t

Werte

EnumeratorBeschreibung
kPhysical=0 UdsMessage is physical addressed.
kFunctional=1 UdsMessage is functional addressed.

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

Record
AUTOSAR/AP/record/SWS_DM_00296
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00296@rel:R25-11#94ca6406
Content hash
94ca6406
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00296
Status: valid/unmigrated Version: rel:R25-11#73c5d74a 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_DM_00296@rel:R25-11#73c5d74a
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#4c5d75c22026-09-30
  • R19-11rel:R19-11#529ba7a62026-10-14
  • R20-11rel:R20-11#1367eab12026-10-14
  • R21-11rel:R21-11#e71fec232026-10-14
  • R22-11rel:R22-11#1b4538a52026-10-14
  • R23-11rel:R23-11#caaa74622026-10-14
  • R24-11rel:R24-11#61f5ce732026-10-14
  • R25-11rel:R25-11#73c5d74a2026-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

类型别名文档

类型别名 Address [SWS_DM_00293] Upstream: RS_Diag_04147

using Address = std::uint16_t;

Type for UDS source and target addresses.

Header-Datei#include "apext/diag/uds_transport/uds_message.h"
Scopeclass apext::diag::uds_transport::UdsMessage
SymbolAddress

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

Record
AUTOSAR/AP/record/SWS_DM_00293
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00293@rel:R25-11#d036dc2e
Content hash
d036dc2e
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00293
Status: valid/unmigrated Version: rel:R25-11#60819fb1 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_DM_00293@rel:R25-11#60819fb1
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#d7355a382026-09-30
  • R19-11rel:R19-11#93b31df92026-10-14
  • R20-11rel:R20-11#405f65e82026-10-14
  • R21-11rel:R21-11#405f65e82026-10-14
  • R22-11rel:R22-11#b1f533352026-10-14
  • R23-11rel:R23-11#69f7dbf82026-10-14
  • R24-11rel:R24-11#5bf59b412026-10-14
  • R25-11rel:R25-11#60819fb12026-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

类型别名 MetaInfoMap [SWS_DM_00294] Upstream: RS_Diag_04147, RS_Diag_04170

using MetaInfoMap = ara::core::Map<ara::core::String, ara::core::String>;

Type for the meta information attached to a UdsMessage.

Header-Datei#include "apext/diag/uds_transport/uds_message.h"
Scopeclass apext::diag::uds_transport::UdsMessage
SymbolMetaInfoMap

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

Record
AUTOSAR/AP/record/SWS_DM_00294
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00294@rel:R25-11#5ac8eb26
Content hash
5ac8eb26
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00294
Status: valid/unmigrated Version: rel:R25-11#0cf88911 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_DM_00294@rel:R25-11#0cf88911
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#be98419a2026-09-30
  • R19-11rel:R19-11#bd65d4472026-10-14
  • R20-11rel:R20-11#6dd1a4672026-10-14
  • R21-11rel:R21-11#6dd1a4672026-10-14
  • R22-11rel:R22-11#cd7575cf2026-10-14
  • R23-11rel:R23-11#b798cc222026-10-14
  • R24-11rel:R24-11#fbebf2ea2026-10-14
  • R25-11rel:R25-11#0cf889112026-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