通过运行时追踪检测汽车安全固件的架构漂移，提升设计与实际行为的一致性。
Detecting Architectural Drift in Safety-Critical Firmware through Runtime Trace Analysis
- 采集硬件辅助执行轨迹，抽象为组件间消息交互
- 在26个测试用例中与专家标注结果高度一致，准确识别缺失、额外等偏差
- 生成可读报告，帮助工程师快速定位问题，适合汽车安全领域从业者
长期运行的安全关键固件中，保持架构设计与实际运行行为的一致性极具挑战。本文提出一种基于运行时信息的架构漂移检测方法，适用于符合ISO 26262标准的固件。该方法通过硬件辅助收集执行轨迹，将其抽象为固件组件间的消息交换，并通过确定性差异分析步骤，将运行时行为与设计阶段的序列图进行比对。计算出的差异可明确标识为确认、缺失、额外或反转四类不一致。进一步采用受限的大型语言模型生成人类可读报告，仅用于支持专家评审。在工业固件场景下，通过一致性验证和实践者调查评估该方法。26个测试案例结果显示，生成的差异与专家标注参考结果高度一致；实践者认为报告有助于理解漂移、减少人工分析工作量，并支持面向安全的文档编写。研究表明，结合运行时追踪分析、确定性架构差异比对与受限大模型报告生成，可在演进中的安全关键固件中有效支持架构漂移检测。
原文摘要 · Abstract (English)
Maintaining consistency between architectural design and runtime-observed behavior is challenging in long-lived safety-critical firmware. This paper presents a runtime-informed methodology for detecting architectural drift in ISO 26262-compliant firmware. The approach collects hardware-assisted execution traces, abstracts them into message exchanges among firmware components, and compares the resulting runtime behavior with design-time sequence diagrams through a deterministic differencing step. The computed delta identifies discrepancies as confirmed, missing, additional, or inverted, while a constrained LLM-based step generates a human-readable report only to support expert review. We evaluate the methodology in an industrial firmware context through agreement-based validation and a practitioner survey. Results over 26 test cases show strong agreement between the generated deltas and expert-curated references, while practitioners perceive the reports as useful for interpreting drift, reducing manual analysis effort, and supporting safety-oriented documentation activities. The findings suggest that combining runtime trace analysis, deterministic architectural differencing, and constrained LLM-based reporting can practically support architectural drift detection in evolving safety-critical firmware.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品；中文卡片由大模型生成，请以原文为准。