DEENESPTFRRUARHIKOZHNL

类 apext::diag::uds_transport::UdsTransportProtocolMgr

[SWS_DM_00306] Upstream: RS_Diag_04147, RS_Diag_04168

class UdsTransportProtocolMgr {...};

The UdsTransportProtocolMgr class manages the interaction between the Diagnostic Server instance(s) and various UDS Transport Protocols (e.g., DoIP[2], CAN[21]). It provides a standard, extensible API for handling transport-specific message reception and optional early payload access.

Literaturverzeichnis SWS Diagnostics: [2] ISO 13400-2:2019 – Road vehicles – Diagnostic communication over Internet Protocol (DoIP) – Part 2: Network and transport layer requirements and services (Edition 2, Release 2019-12) – www.iso.org
[21] ISO 15765-2 – Road vehicles – Diagnostics on Controller Area Networks (CAN) – Part2: Network layer services

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

用户指南人工智能生成

协调传输层插件与 Diagnostic Server 会话层之间的 UDS 消息交换。
AI 生成 未审核 模型: gemini-3.8-flash-medium · 推理强度: medium · 温度: 不可控 · 提示词: d6f6643e28ac 来源 未决问题(2)
译自德文指南gemini-3.8-flash-low · 2026-10-13 · 德文原文

协调传输层插件与 Diagnostic Server 会话层之间的 UDS 消息交换。

类 apext::diag::uds_transport::UdsTransportProtocolMgr 根据 AUTOSAR AP SWS Diagnostics §7.1.1 “Support of UDS Transport Layer” 管理 Diagnostic Server 与特定 UDS 传输协议之间的交互。它通过预指示和向会话层的异步转发来控制两阶段消息接收,并控制发送事件与生命周期事件([SWS_DM_00309]、[SWS_DM_00311])的反馈。所有接口调用均设计为异常安全,但非线程安全。

上下文

类 apext::diag::uds_transport::UdsTransportProtocolMgr 充当 Diagnostic Server 实例或 DM-Core(会话层)与符合 AUTOSAR AP SWS Diagnostics §7.1.1 “Support of UDS Transport Layer” 的各种 UDS 传输协议(如 DoIP 或 CAN)之间的核心中介。它提供了一个可扩展接口,派生自基类 UdsTransportProtocolHandler 的具体实现传输插件([SWS_DM_00315])可通过该接口报告传入的 UDS 消息并将传输确认转发给诊断核心。Interpretation:该管理器实例大概率由 Diagnostic Management 作为长期运行的中介组件运行,以便统一整合各类异构传输接口。 问题 Q-79e155960156d04a (未决)

MgrKontext SessionLayer Session Layer (DM Core) Mgr UdsTransportProtocolMgr Mgr->SessionLayer T_Data.ind Handler UdsTransportProtocolHandler Handler->Mgr IndicateMessage / HandleMessage Handler->Mgr TransmitConfirmation Handler->Mgr HandlerStopped / ChannelReestablished PeriodicHandler UdsTransportProtocolPeriodicHandler PeriodicHandler->Mgr PeriodicTransmitConfirmation

上下文图:UdsTransportProtocolMgr 嵌入在传输层处理程序与会话层之间。来源:[SWS_DM_00309]、[SWS_DM_00311]、[SWS_DM_00312]、[SWS_DM_01069]、AUTOSAR AP SWS Diagnostics §7.1.1 “Support of UDS Transport Layer”。

生命周期

销毁通过虚析构函数 ~UdsTransportProtocolMgr() 执行,该析构函数被指定为 noexcept = default([SWS_DM_01524])。在运行期间,管理器根据 AUTOSAR AP SWS Diagnostics §7.1.1.1 “Initialization, Starting and Stopping of a UDS TransportLayer” 和 [SWS_DM_00329] 响应已注册传输协议处理程序的生命周期事件:若处理程序关闭,它会通过 HandlerStopped()([SWS_DM_00314])向管理器报告完成。若先前断开连接的通道再次可用,则在预先通过 ChannelReestablished() 激活后,通过指定 GlobalChannelIdentifier 将此情况告知管理器([SWS_DM_00313]、[SWS_DM_09021])。

关于所有权,消息处理时适用基于 unique pointer 语义的严格缓冲区传递:诊断核心在通告消息时创建对象 UdsMessagePtr,并将其临时移交给处理程序进行填充([SWS_DM_00309])。在成功接收或传输中止时,消息的所有权将完全归还给通用 DM 核心([SWS_DM_00310]、[SWS_DM_00311])。该接口的所有回调方法均归类为异常安全(noexcept),但明确归类为非线程安全([SWS_DM_00309]、[SWS_DM_00311])。

使用路径

常规的 UDS 消息接收流程分为两个连续阶段。首先,传输处理程序通过 IndicateMessage() 指示消息的开始([SWS_DM_00309])。此时会传递源地址和目标地址、寻址类型(物理或功能)、通道 ID、总大小以及前几个有效负载字节的视图(payloadInfo)。该预先信息允许诊断核心提前评估请求,例如用于识别功能性 Tester Present([SWS_DM_00309])。如果核心接受该请求,管理器将返回由 IndicationResult::kIndicationOk 和待填充的消息缓冲区组成的对。

一旦传输处理程序接收到完整消息,便通过 HandleMessage() 将其转发给会话层([SWS_DM_00311])。这对应于 ISO 14229-2 中的原语 T_Data.ind。Interpretation:要求 HandleMessage() 立即返回大概率是通过移交给会话层的内部队列来实现的,因为实际处理必须在后台异步执行([SWS_DM_00311])。出站传输在完成后由处理程序通过 TransmitConfirmation() 进行确认([SWS_DM_00312]),而周期性消息则通过 PeriodicTransmitConfirmation() 确认([SWS_DM_01069])。 问题 Q-b6e97504ca3a3a95 (未决)

UDS 消息接收流程UdsTransportProtocolHandlerUdsTransportProtocolMgrSession LayerUse Case: 消息通告IndicateMessage(sourceAddr, targetAddr, type, channel, size, payloadInfo)Puffer anfordern & Validierungstd::pair(kIndicationOk, messagePtr)std::pair(kIndicationOk, messagePtr)Use Case: 数据接收与传递Nutzdaten in message schreibenHandleMessage(messagePtr)T_Data.ind(messagePtr)立即返回(异步)返回

时序图:通过 IndicateMessage 和 HandleMessage 进行 UDS 消息接收的典型流程。来源:[SWS_DM_00309]、[SWS_DM_00311]。

错误场景

若 DM 核心无法接受通告的消息,则 IndicateMessage() 便会失败。枚举 IndicationResult 为此定义了错误原因 kIndicationOccupied(通道繁忙)、kIndicationOverflow(缓冲区溢出)或 kIndicationUnknownTargetAddress(未知目标地址),随后将不提供消息缓冲区([SWS_DM_00309]、[SWS_DM_00384])。

如果在成功指示后,在传输层级别的后续传输期间发生错误,导致无法再形成 HandleMessage(),则处理程序必须强制调用 NotifyMessageFailure()([SWS_DM_00310])。由此,先前分配的消息缓冲区将受控地归还给会话层并释放。在发送操作中,TransmitConfirmation() 通过 TransmissionResult 报告结果;若在网络层发送失败,则传输 kTransmitFailed([SWS_DM_00307]、[SWS_DM_00312])。

本指南仅基于 AUTOSAR R25-11 规范。

成员图

KI-gestützte Gruppierung auf Basis der Records und Spezifikationsauszüge; keine Gliederung aus der AUTOSAR-Spezifikation.

类图

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

G napext__diag__uds_transport__UdsTransportProtocolMgr247 UdsTransportProtocolMgr + ~UdsTransportProtocolMgr() + ChannelReestablished() + HandleMessage() + HandlerStopped() + IndicateMessage() + NotifyMessageFailure() + PeriodicTransmitConfirmation() + TransmitConfirmation()

详细视图

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

Objektlebenszyklus

Destructor of class UdsTransportProtocolMgr.

virtual ~UdsTransportProtocolMgr () noexcept=default;

Nachrichtenempfang

Hands over a valid received UDS message (currently this is only a request type) from the Transport Layer to the Session Layer. This corresponds to T_Data.ind of Figure 2 from ISO 14229-2[25]. The behavior is asynchronously, i.e. the UDS Message is handed over to the Session Layer and it is expected, that it "instantly" returns, which means, that real processing of the message shall be done asynchronously by the Transport Layer!

virtual void HandleMessage (UdsMessagePtr message) noexcept=0;

Indicates a message start. This is an interface, which is just served/called by UdsTransportProtocolHandlers, which return TRUE from UdsTransportProtocolHandlers::isStartOfMessageIndicationSupported().

virtual std::pair< IndicationResult, UdsMessagePtr > IndicateMessage ( UdsMessage::Address sourceAddr, UdsMessage::Address targetAddr, Uds Message::TargetAddressType type, GlobalChannelIdentifier globalChannel Id, std::size_t size, ara::core::Span< const std::uint8_t > payload Info) noexcept=0;

Allowed return values from the DM Server to the Transport Protocol Handler Instance for the received IndicateMessage.

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

Fehlerbehandlung

Indicates, that the message indicated via IndicateMessage() has failure and will not lead to a final HandleMessage() call.

virtual void NotifyMessageFailure (UdsMessagePtr message) noexcept=0;

Sendebestätigung

Confirmation of sent messages and number.

virtual void PeriodicTransmitConfirmation (ara::core::Vector< Uds MessageConstPtr > messages, std::size_t numberOfSentMessages) noexcept=0;

Notification about the outcome of a transmit request called by core DM at the handler via Uds TransportProtocolHandler::Transmit(). This transmit API covers T_Data.con of ISO 14229-2[25] Figure 2.

virtual void TransmitConfirmation (UdsMessageConstPtr message, TransmissionResult result) noexcept=0;

Values denoting the Transmission Confirmation Result provided by the Transport Protocol Handler Instance to the DM Server.

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

Kanal- und Handlersteuerung

Notification call from the given transport protocol channel, that it has been reestablished since the last (Re)Start from the UdsTransportProtocolHandler to which this channel belongs. To activate this notification a previous call to UdsTransportProtocolHandler::Notify Reestablishment() has to be done. See further documentation at UdsTransport ProtocolHandler::NotifyReestablishment().

virtual void ChannelReestablished (GlobalChannelIdentifier global ChannelId) noexcept=0;

Notification call from handler, that it has stopped now (e.g. closed down network connections, freed resources, etc...) This callback is expected as a reaction from handler to a call to UdsTransportProtocol Handler::Stop().

virtual void HandlerStopped (UdsTransportProtocolHandlerID handlerId) noexcept=0;

Type of tuple to pack UdsTransportProtocolHandlerID and ChannelID together, to form a global unique (among all used UdsTransportProtocolHandlers within DM) identifier of a Uds TransportProtocol channel.

using GlobalChannelIdentifier = std::tuple<UdsTransportProtocolHandler ID, ChannelID>;

方法文档

函数 ChannelReestablished [SWS_DM_00313] Upstream: RS_AP_00120, RS_AP_00121, RS_AP_00122, RS_Diag_04147, RS_Diag_04168

virtual void ChannelReestablished (GlobalChannelIdentifier global ChannelId) noexcept=0;

Notification call from the given transport protocol channel, that it has been reestablished since the last (Re)Start from the UdsTransportProtocolHandler to which this channel belongs. To activate this notification a previous call to UdsTransportProtocolHandler::Notify Reestablishment() has to be done. See further documentation at UdsTransport ProtocolHandler::NotifyReestablishment().

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

使用

类 apext::diag::uds_transport::UdsTransportProtocolMgr 的方法 ChannelReestablished 用作 UDS 传输协议实现向 Diagnostic Management (DM) 的反馈,表明通信通道在(重新)启动后再次可用 [SWS_DM_00313]。一旦检测到由 ChannelID 表示的网络通道重新可用,传输协议实现就恰好调用此方法一次 [SWS_DM_00358]。作为参数传递 globalChannelId,其由自身 handlerIdent 与 ChannelID 组成的元组构成 [SWS_DM_00358]。

交互和生命周期

通知的前提条件是先前调用过 NotifyReestablishment [SWS_DM_00313],[SWS_DM_00356]。典型的用例是执行 ECU 重置(UDS 服务 0x11)并带有在重启后发送肯定响应的选项 [SWS_DM_00326]。为了确保在 DM 重启后也能收到通知,通知请求必须由传输协议进行持久化存储 [SWS_DM_00359]。

错误处理与并发

该函数没有返回值,并被指定为 noexcept(exception safe)[SWS_DM_00313]。由于该接口被归类为非线程安全(not thread-safe)[SWS_DM_00313],调用处理程序可能必须对访问进行外部同步。 问题 Q-aaf14893457cceb6 (未决)作为时间限制,DM 仅在调用 UdsTransportProtocolHandler::Start 之后才允许处理对 ChannelReestablished 的调用 [SWS_DM_01744]。

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

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

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

Parameter (in)

ParameterBeschreibung
globalChannelIdtransport protocol channel, which is available again.

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_DM_00313
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00313@rel:R25-11#bad7f6fd
Content hash
bad7f6fd
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00313
Status: valid/unmigrated Version: rel:R25-11#4c5b70ac 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_00313@rel:R25-11#4c5b70ac
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#dacc8bb22026-09-30
  • R19-11rel:R19-11#acd4155f2026-10-14
  • R20-11rel:R20-11#9235fd502026-10-14
  • R21-11rel:R21-11#b392eb2d2026-10-14
  • R22-11rel:R22-11#b01162a42026-10-14
  • R23-11rel:R23-11#f88cee172026-10-14
  • R24-11rel:R24-11#867edbc12026-10-14
  • R25-11rel:R25-11#4c5b70ac2026-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

函数 HandleMessage [SWS_DM_00311] Upstream: RS_Diag_04147, RS_Diag_04168

virtual void HandleMessage (UdsMessagePtr message) noexcept=0;

Hands over a valid received UDS message (currently this is only a request type) from the Transport Layer to the Session Layer. This corresponds to T_Data.ind of Figure 2 from ISO 14229-2[25]. The behavior is asynchronously, i.e. the UDS Message is handed over to the Session Layer and it is expected, that it "instantly" returns, which means, that real processing of the message shall be done asynchronously by the Transport Layer!

Literaturverzeichnis SWS Diagnostics: [25] ISO 14229-2(2021) – Unified diagnostic services (UDS) - Part 2: Session layer services (Release 2021-10) – www.iso.org

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

方法 HandleMessage 用于将完整接收到的有效 UDS 请求消息从传输层传递到诊断管理的会话层([SWS_DM_00311])。这对应于符合 ISO 14229-2 的服务 T_Data.ind([SWS_DM_00311]、AUTOSAR_AP_SWS_Diagnostics §C.2.1.2.2.2 “HandleMessage”)。

调用与参数

一旦传输协议实现填充了先前通过 IndicateMessage 请求的缓冲区的有效负载([SWS_DM_00388]),它就会在 apext::diag::uds_transport::UdsTransportProtocolMgr 的实例上调用 HandleMessage([SWS_DM_00345])。类型为 UdsMessagePtr 的 message 作为实参传递。通过 std::unique_ptr 语义,UDS 消息的所有权返回给通用 DM 核心([SWS_DM_00311])。该函数不提供返回值。

语义、并发与错误处理

  • 异步性:该调用必须立即返回(“instantly returns”)([SWS_DM_00311])。解释:诊断请求的实际处理可能在 DM 核心中的独立执行上下文中异步继续进行。 问题 Q-b8dd1a5f3d2dcdf0 (未决)
  • 错误情况:该方法被声明为 noexcept 且异常安全([SWS_DM_00311])。如果消息的接收或填充失败,则不得调用 HandleMessage;而必须通过 NotifyMessageFailure 报告错误([SWS_DM_00310])。
  • 线程安全性:该操作被指定为 not thread-safe([SWS_DM_00311])。调用方必须同步对同一实例的并行访问。

相互作用

该接口属于传输协议层,应与应用侧的服务处理方法 ara::diag::GenericUDSService::HandleMessage([SWS_DM_00618])区分开来。

本文档自动生成。所有说明均仅基于 R25-11 规范版本。

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

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

Parameter (in)

ParameterBeschreibung
messageThe UDS message ptr (unique_ptr semantics) with the request. Ownership of the UDS Message is given back to the generic DM core here.

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_DM_00311
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00311@rel:R25-11#0191957c
Content hash
0191957c
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00311
Status: valid/unmigrated Version: rel:R25-11#25c5615f 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_00311@rel:R25-11#25c5615f
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#1d9aefcf2026-09-30
  • R19-11rel:R19-11#cb8d6db52026-10-14
  • R20-11rel:R20-11#307c47612026-10-14
  • R21-11rel:R21-11#307c47612026-10-14
  • R22-11rel:R22-11#fd0648c82026-10-14
  • R23-11rel:R23-11#4d3583a52026-10-14
  • R24-11rel:R24-11#779e87e62026-10-14
  • R25-11rel:R25-11#25c5615f2026-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

函数 HandlerStopped [SWS_DM_00314] Upstream: RS_AP_00120, RS_AP_00121, RS_AP_00122, RS_Diag_04147, RS_Diag_04168

virtual void HandlerStopped (UdsTransportProtocolHandlerID handlerId) noexcept=0;

Notification call from handler, that it has stopped now (e.g. closed down network connections, freed resources, etc...) This callback is expected as a reaction from handler to a call to UdsTransportProtocol Handler::Stop().

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

管理接口 apext::diag::uds_transport::UdsTransportProtocolMgr 的纯虚回调方法 HandlerStopped 用作 UDS 传输插件对 Diagnostic Manager (DM) 的反馈,表明其执行已终止,且所有关联资源及网络连接已完全释放 [SWS_DM_00314]。该调用被预期为处理程序对先前调用 UdsTransportProtocolHandler::Stop() 的强制响应 [SWS_DM_00314], [SWS_DM_00323]。

调用上下文与参数:受影响的插件在调用时通过类型为 UdsTransportProtocolHandlerID 的输入参数 handlerId 标识自身 [SWS_DM_00314]。该方法没有返回值(void),并通过指定为 noexcept 确保了完全的异常安全性(exception safe)[SWS_DM_00314]。未为此接口定义特定的错误码、错误反应或向 DET 或 DEM 的报告。

流程与限制:如果 Diagnostic Manager 在关闭过程中转换为状态 ApplicationState.kTerminating,它首先在每个已启动的 UDS 传输协议实现上调用 Stop() [SWS_DM_00333]。从 Stop() 返回后,适用严格的调用禁止:除了 HandlerStopped [SWS_DM_01741], [SWS_DM_00323] 之外,处理程序插件不得再针对 UdsTransportProtocolMgr 调用任何其他方法。在最终终止 DM 进程之前,DM 会等待具有匹配 handlerId 的相应 HandlerStopped 回调到达 [SWS_DM_00340]。该接口被标明为非线程安全(not thread-safe)[SWS_DM_00314]。解释:由于 DM 单独等待回调的到达,插件中网络连接的实际终止大概率与 Stop() 方法的返回异步发生。 问题 Q-40829d46bd661337 (未决)

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

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

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

Parameter (in)

ParameterBeschreibung
handlerIdindication, which plugin stopped.

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_DM_00314
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00314@rel:R25-11#a74e727a
Content hash
a74e727a
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00314
Status: valid/unmigrated Version: rel:R25-11#0cc2f185 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_00314@rel:R25-11#0cc2f185
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#8489c37a2026-09-30
  • R19-11rel:R19-11#4212b1402026-10-14
  • R20-11rel:R20-11#f5d072332026-10-14
  • R21-11rel:R21-11#d2e1ff562026-10-14
  • R22-11rel:R22-11#0b5685c52026-10-14
  • R23-11rel:R23-11#43fb4c882026-10-14
  • R24-11rel:R24-11#33d1abec2026-10-14
  • R25-11rel:R25-11#0cc2f1852026-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

函数 IndicateMessage [SWS_DM_00309] Upstream: RS_AP_00120, RS_AP_00121, RS_AP_00122, RS_Diag_04147, RS_Diag_04168

virtual std::pair< IndicationResult, UdsMessagePtr > IndicateMessage ( UdsMessage::Address sourceAddr, UdsMessage::Address targetAddr, Uds Message::TargetAddressType type, GlobalChannelIdentifier globalChannel Id, std::size_t size, ara::core::Span< const std::uint8_t > payload Info) noexcept=0;

Indicates a message start. This is an interface, which is just served/called by UdsTransportProtocolHandlers, which return TRUE from UdsTransportProtocolHandlers::isStartOfMessageIndicationSupported().

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

当要指示开始接收 UDS 消息且处理程序支持此操作时,UdsTransportProtocolHandler 会同步调用类 apext::diag::uds_transport::UdsTransportProtocolMgr 的方法 IndicateMessage [SWS_DM_00309]。调用者传入源地址和目标地址(sourceAddr、targetAddr)、寻址类型 type(物理或功能)、通道 ID globalChannelId、预期的总大小 size 以及可选的已接收有效负载数据的字节视图(payloadInfo)。建议在 payloadInfo 中提供至少两个字节,以便 Diagnostic Management Core 即使在正在进行的流处理过程中也能识别诸如 Tester-Present(旁路逻辑)等功能请求 AUTOSAR_AP_SWS_Diagnostics §7.1 “UDS Transport Layer”。

作为返回值,此同步且异常安全的调用提供由 IndicationResult [SWS_DM_00384] 和 UdsMessagePtr [SWS_DM_00309] 组成的 std::pair:

  • 接受:如果可以处理该消息,DM Core 将返回 IndicationResult::kIndicationOk 以及有效的 UdsMessagePtr,后者的最小容量至少为一字节 [SWS_DM_00385]。
  • 拒绝和错误情况:如果 DM 处于忙碌状态,它将以 kIndicationOccupied 和 nullptr 进行响应 [SWS_DM_00386]。如果目标地址无效,则返回带有空指针的 kIndicationUnknownTargetAddress。其他定义的状态值为 kIndicationOverflow [SWS_DM_00384]。

关于并发性和生命周期,该方法被指定为非线程安全(not thread-safe)[SWS_DM_00309];因此调用必须相应地同步进行。通过 payloadInfo 传入的视图是瞬态的,并且仅可在该函数调用内部使用 [SWS_DM_00309]。

在后续流程中,若返回 kIndicationOk,传输层将通过 GetPayload [SWS_DM_00301] 填充所提供的缓冲区直至达到容量上限或完整消息长度 [SWS_DM_00388]。成功填充后将调用 HandleMessage [SWS_DM_00345]。如果消息接收提前失败,则处理程序必须通过 NotifyMessageFailure [SWS_DM_00310] 将缓冲区归还给 DM。

该文本由 AI 生成,用作参考指引。

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

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

Parameter (in)

ParameterBeschreibung
sourceAddrUDS source address of the message.
targetAddrUDS target address of the message.
typeIndication whether the request is kPhysical or kFunctional addressed.
globalChannelIdTransport Protocol Channel on which the message start happened.
sizeSize in bytes of the UdsMessage starting from SID.
payloadInfoView onto the first received payload bytes, if any. This view shall be used only within this function call. It is recommended that the Transport Protocol provides at least the first two bytes of the request message, so the DM can identify a functional Tester Present. Lifetime: Valid until Promise is fulfilled or the processing is cancelled by the cancellationHandler.

Rückgabewert

TypBeschreibung
std::pair< IndicationResult, UdsMessagePtr>Pair of IndicationResult and a pointer to UDS Message owned/created by DM core and returned to the handler to get filled.

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

Record
AUTOSAR/AP/record/SWS_DM_00309
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00309@rel:R25-11#111b4a44
Content hash
111b4a44
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00309
Status: valid/unmigrated Version: rel:R25-11#38e7de31 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_00309@rel:R25-11#38e7de31
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#04055a8d2026-09-30
  • R19-11rel:R19-11#bfb192392026-10-14
  • R20-11rel:R20-11#8e14a6b72026-10-14
  • R21-11rel:R21-11#66a0b1c12026-10-14
  • R22-11rel:R22-11#2f212c252026-10-14
  • R23-11rel:R23-11#1d9e17452026-10-14
  • R24-11rel:R24-11#674af7dd2026-10-14
  • R25-11rel:R25-11#38e7de312026-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

函数 NotifyMessageFailure [SWS_DM_00310] Upstream: RS_Diag_04147, RS_Diag_04168

virtual void NotifyMessageFailure (UdsMessagePtr message) noexcept=0;

Indicates, that the message indicated via IndicateMessage() has failure and will not lead to a final HandleMessage() call.

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

使用

纯虚方法 NotifyMessageFailure 通过头文件 apext/diag/uds_transport/protocol_mgr.h 在接口 apext::diag::uds_transport::UdsTransportProtocolMgr 中提供 [SWS_DM_00310]。它用于传输协议实现向 Diagnostic Management 指示:先前通过 IndicateMessage() 发出信号的消息已失败,并且不会再对 HandleMessage() [SWS_DM_00345] 进行最终调用 [SWS_DM_00310]。类型为 UdsMessagePtr 的指针 message 作为参数传递,由此受影响的消息被传回会话层 [SWS_DM_00310]。不存在返回值(void)。

错误处理与并发

该函数被声明为 noexcept 且异常安全 [SWS_DM_00310]。它不抛出异常,并纯粹通过参数接口报告传输中止。关于并发性,该方法被归类为非线程安全(not thread-safe) [SWS_DM_00310]。解释:在传输协议层进行并行处理时,调用者可能必须确保外部同步。 问题 Q-8d9b3a3561b9b6ac (未决)

交互与流程

在常规流程中,在成功的 IndicateMessage() 之后,传输协议填充 UdsMessage [SWS_DM_00388] 的有效负载,并通过 HandleMessage() 将其转发给 Diagnostic Management [SWS_DM_00345]。然而,如果传输失败(例如在接收多帧请求期间发生错误),则改为调用 NotifyMessageFailure [SWS_DM_00310]。这可以防止后续的处理调用并影响会话管理:虽然 S3Server 定时器在接收开始时停止 [SWS_DM_00383],但多帧消息的接收错误会导致 S3Server 定时器被重置并从头开始重新计数(SWS Diagnostics §7.3.2.7 “Session handling” / [SWS_DM_00310])。

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

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

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

Parameter (in)

ParameterBeschreibung
messagePointer to the UDS Message handed back over to the Session Layer.

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_DM_00310
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00310@rel:R25-11#e33732fe
Content hash
e33732fe
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00310
Status: valid/unmigrated Version: rel:R25-11#533ed88a 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_00310@rel:R25-11#533ed88a
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#e7beffc22026-09-30
  • R19-11rel:R19-11#bf0753592026-10-14
  • R20-11rel:R20-11#126bf37a2026-10-14
  • R21-11rel:R21-11#da1ddcf72026-10-14
  • R22-11rel:R22-11#f198f39e2026-10-14
  • R23-11rel:R23-11#501c9dff2026-10-14
  • R24-11rel:R24-11#c8c1a8962026-10-14
  • R25-11rel:R25-11#533ed88a2026-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

函数 PeriodicTransmitConfirmation [SWS_DM_01069] Upstream: RS_Diag_04215

virtual void PeriodicTransmitConfirmation (ara::core::Vector< Uds MessageConstPtr > messages, std::size_t numberOfSentMessages) noexcept=0;

Confirmation of sent messages and number.

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

使用

纯虚方法 PeriodicTransmitConfirmation 是类 apext::diag::uds_transport::UdsTransportProtocolMgr 的组成部分,并通过头文件 apext/diag/uds_transport/protocol_mgr.h 声明 [SWS_DM_01069]。它用于确认已发送的周期性诊断报文,并传输成功发送的报文数量 AUTOSAR_AP_SWS_Diagnostics §C.2.1.2.2.6 “PeriodicTransmitConfirmation”。

调用时传递两个输入参数,而该方法不提供返回值:

  • messages (ara::core::Vector<UdsMessageConstPtr>):先前传递给方法 UdsTransportProtocolPeriodicHandler::PeriodicTransmit() 的同一报文有序列表 [SWS_DM_01069]。
  • numberOfSentMessages (std::size_t):从列表 messages 中成功传输的报文数量 [SWS_DM_01069]。

错误处理与异常安全性

关于异常安全性,该接口被指定为 exception safe,并带有说明符 noexcept [SWS_DM_01069]。因此,它不会抛出任何 C++ 异常。规范中未为此确认函数定义特定的错误码或通过 DET 或 DEM 发送的错误消息。

并发性与边界条件

根据规范,该函数被归类为非线程安全(not thread-safe)[SWS_DM_01069]。因此,对同一实例的并发调用未受保护,必须由调用方进行协调。

相互作用

该函数直接衔接周期性发送流程:在调用 UdsTransportProtocolPeriodicHandler::PeriodicTransmit() 后,它接收关于实际发出报文的确认 AUTOSAR_AP_SWS_Diagnostics §C.2.1.2.2.6 “PeriodicTransmitConfirmation”。在需求层面,该函数归属于上游需求 RS_Diag_04215 [SWS_DM_01069]。

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

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

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

Parameter (in)

ParameterBeschreibung
messagesThe same ordered list of messages previously passed to Uds TransportProtocolPeriodicHandler::Periodic Transmit().
numberOfSentMessagesThe number of successfully sent messages from the "messages" list.

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_DM_01069
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01069@rel:R25-11#5955b4ac
Content hash
5955b4ac
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01069
Status: valid/unmigrated Version: rel:R25-11#53ff341c 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_DM_01069@rel:R25-11#53ff341c
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#bcf47ee92026-09-30
  • R20-11rel:R20-11#92ace4d82026-10-14
  • R21-11rel:R21-11#cd6fd2542026-10-14
  • R22-11rel:R22-11#55d5fcb22026-10-14
  • R23-11rel:R23-11#389cb5052026-10-14
  • R24-11rel:R24-11#986d318f2026-10-14
  • R25-11rel:R25-11#53ff341c2026-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

函数 TransmitConfirmation [SWS_DM_00312] Upstream: RS_Diag_04172, RS_Diag_04147, RS_Diag_04168

virtual void TransmitConfirmation (UdsMessageConstPtr message, TransmissionResult result) noexcept=0;

Notification about the outcome of a transmit request called by core DM at the handler via Uds TransportProtocolHandler::Transmit(). This transmit API covers T_Data.con of ISO 14229-2[25] Figure 2.

Literaturverzeichnis SWS Diagnostics: [25] ISO 14229-2(2021) – Unified diagnostic services (UDS) - Part 2: Session layer services (Release 2021-10) – www.iso.org

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

使用

接口 apext::diag::uds_transport::UdsTransportProtocolMgr 的纯虚方法 TransmitConfirmation 用于向 Diagnostic Management (DM) 通知由 DM 先前通过 UdsTransportProtocolHandler::Transmit 发起的发送任务的完成情况 [SWS_DM_00312] [SWS_DM_00348]。该函数实现了符合 ISO 14229-2 的原语服务 T_Data.con [SWS_DM_00312]。

调用时会传递两个参数 [SWS_DM_00312]:

  • message(UdsMessageConstPtr):指向先前在 IndicateMessage() 中提供且其传输已被确认的 UDS 消息的指针 [SWS_DM_00312]。
  • result(TransmissionResult):指示传输结果。如果网络层能够成功将 UDS 响应输出到网络上,则该值应设置为 kTransmitOk,否则设置为 kTransmitFailed [SWS_DM_00351] SWS Diagnostics §7.1.1.3 “Confirmation Result”。

该方法没有返回值(void),并且被声明为 noexcept,因此必须以异常安全的方式执行 [SWS_DM_00312]。

并发性与系统行为

该接口被明确指定为非线程安全 [SWS_DM_00312]。因此,来自并发网络或处理程序上下文的调用可能需要通过传输协议实现进行外部同步。 问题 Q-e540ca89c3f61ecb (未决)

此外,该调用还会影响身份验证管理:如果客户端处于默认会话且处于状态 kAuthenticated,则如果在最后一次 TransmitConfirmation 之后持续 authenticationTimeout 时间未收到新请求,Diagnostic Server 会将其置于状态 kDeAuthenticated [SWS_DM_01210]。

本段文本由 AI 生成,用于技术指导。

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

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

Parameter (in)

ParameterBeschreibung
messageFor which message (created in IndicateMessage()) this is the confirmation.
resultResult of transmission. In case the UDS message could be transmitted on network layer kTransmitOk, else kTransmitFailed.

Rückgabewert

TypBeschreibung
None

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

Record
AUTOSAR/AP/record/SWS_DM_00312
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00312@rel:R25-11#66439932
Content hash
66439932
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00312
Status: valid/unmigrated Version: rel:R25-11#222a75d3 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_00312@rel:R25-11#222a75d3
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#677d428f2026-09-30
  • R19-11rel:R19-11#212d61dd2026-10-14
  • R20-11rel:R20-11#a10ea9422026-10-14
  • R21-11rel:R21-11#71d0b62f2026-10-14
  • R22-11rel:R22-11#550859bf2026-10-14
  • R23-11rel:R23-11#54312aac2026-10-14
  • R24-11rel:R24-11#9aca7ec12026-10-14
  • R25-11rel:R25-11#222a75d32026-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

函数 ~UdsTransportProtocolMgr [SWS_DM_01524] Upstream: RS_AP_00134

virtual ~UdsTransportProtocolMgr () noexcept=default;

Destructor of class UdsTransportProtocolMgr.

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

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

Record
AUTOSAR/AP/record/SWS_DM_01524
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01524@rel:R25-11#ada3c67a
Content hash
ada3c67a
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01524
Status: valid/unmigrated Version: rel:R25-11#573fe30c 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_01524@rel:R25-11#573fe30c
Point-in-Time History:
Recorded Revisions (5):
  • R25-11rel:R25-11#49e2bed92026-09-30
  • R22-11rel:R22-11#d451921a2026-10-14
  • R23-11rel:R23-11#91e882962026-10-14
  • R24-11rel:R24-11#df6540502026-10-14
  • R25-11rel:R25-11#573fe30c2026-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

枚举文档

枚举 IndicationResult [SWS_DM_00384] Upstream: RS_Diag_04147, RS_Diag_04168

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

Allowed return values from the DM Server to the Transport Protocol Handler Instance for the received IndicateMessage.

Header-Datei#include "apext/diag/uds_transport/protocol_mgr.h"
Forwarding-Header#include "apext/diag/diag_fwd.h"
Scopeclass apext::diag::uds_transport::UdsTransportProtocolMgr
SymbolIndicationResult
Basistypstd::uint8_t

Werte

EnumeratorBeschreibung
kIndicationOk=0 Indication Ok.
kIndicationOccupied=1 Indication Occupied.
kIndicationOverflow=2 Indication Overflow.
kIndicationUnknownTargetAddress=3 Indication UnknownTargetAddress.

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

Record
AUTOSAR/AP/record/SWS_DM_00384
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00384@rel:R25-11#25efc972
Content hash
25efc972
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00384
Status: valid/unmigrated Version: rel:R25-11#fc9e7b47 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_00384@rel:R25-11#fc9e7b47
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#a696d1622026-09-30
  • R19-11rel:R19-11#d4b8e2312026-10-14
  • R20-11rel:R20-11#099ea9052026-10-14
  • R21-11rel:R21-11#b33d8fec2026-10-14
  • R22-11rel:R22-11#ecd3c6072026-10-14
  • R23-11rel:R23-11#707e152a2026-10-14
  • R24-11rel:R24-11#4437e4182026-10-14
  • R25-11rel:R25-11#fc9e7b472026-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

枚举 TransmissionResult [SWS_DM_00307] Upstream: RS_Diag_04172, RS_Diag_04147, RS_Diag_04168

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

Values denoting the Transmission Confirmation Result provided by the Transport Protocol Handler Instance to the DM Server.

Header-Datei#include "apext/diag/uds_transport/protocol_mgr.h"
Forwarding-Header#include "apext/diag/diag_fwd.h"
Scopeclass apext::diag::uds_transport::UdsTransportProtocolMgr
SymbolTransmissionResult
Basistypstd::uint8_t

Werte

EnumeratorBeschreibung
kTransmitOk=0 Transmission Ok.
kTransmitFailed=1 Transmission Failed.

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

Record
AUTOSAR/AP/record/SWS_DM_00307
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_00307@rel:R25-11#ab3ada5f
Content hash
ab3ada5f
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_00307
Status: valid/unmigrated Version: rel:R25-11#a96e1afe 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_00307@rel:R25-11#a96e1afe
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#bb7c59332026-09-30
  • R19-11rel:R19-11#3c5bd3e02026-10-14
  • R20-11rel:R20-11#1a40da8a2026-10-14
  • R21-11rel:R21-11#1a40da8a2026-10-14
  • R22-11rel:R22-11#dd385c782026-10-14
  • R23-11rel:R23-11#d63bd68e2026-10-14
  • R24-11rel:R24-11#0774c6bd2026-10-14
  • R25-11rel:R25-11#a96e1afe2026-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

类型别名文档

类型别名 GlobalChannelIdentifier [SWS_DM_09021] Upstream: RS_Diag_04147, RS_Diag_04168

using GlobalChannelIdentifier = std::tuple<UdsTransportProtocolHandler ID, ChannelID>;

Type of tuple to pack UdsTransportProtocolHandlerID and ChannelID together, to form a global unique (among all used UdsTransportProtocolHandlers within DM) identifier of a Uds TransportProtocol channel.

Header-Datei#include "apext/diag/uds_transport/protocol_mgr.h"
Scopeclass apext::diag::uds_transport::UdsTransportProtocolMgr
SymbolGlobalChannelIdentifier

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

Record
AUTOSAR/AP/record/SWS_DM_09021
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_09021@rel:R25-11#9e11af61
Content hash
9e11af61
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_09021
Status: valid/unmigrated Version: rel:R25-11#2dd38493 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_09021@rel:R25-11#2dd38493
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#4200e9d42026-09-30
  • R19-11rel:R19-11#7c3bef962026-10-14
  • R20-11rel:R20-11#8ffd78d52026-10-14
  • R21-11rel:R21-11#8ffd78d52026-10-14
  • R22-11rel:R22-11#b1e43aa62026-10-14
  • R23-11rel:R23-11#01454d8f2026-10-14
  • R24-11rel:R24-11#1fe1cbb92026-10-14
  • R25-11rel:R25-11#2dd384932026-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