Multi-View Trust Evaluation for Collaborator Selection via Evidential Deep Learning

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2608.25235v1 Announce Type: cross Abstract: Selection of trustworthy collaborators in distributed systems is critical for efficient task completion, necessitating the inference of trustworthiness from their past collaboration experience. However, as a collaborator serves distinct devices across diverse scenarios in past collaborations, its trust-related data, observed from different device-specific views, is inherently multi-source, heterogeneous, and uneven in quality. Consequently, achieving accurate trust evaluations for collaborator selection remains a major challenge. To tackle these issues, we propose a novel multi-view evidential learning (MVE) based trust evaluation method. First, to accommodate the multi-source heterogeneity of observed trust-related data, we model each task owner who has interacted with a potential collaborator as an independent observational view, enabling the evaluation of the collaborator's view-specific trust. Second, to address the dynamic evolution of trust under changing conditions, we leverage the powerful long-sequence modeling capability of the Mamba model to capture the deep temporal patterns of a collaborator's trust state within each view. Furthermore, to quantify the certainty levels of view-specific trust assessments, we incorporate an evidential deep learning mechanism in MVE, which outputs trust evaluation results while quantifying the subjective uncertainty underlying them. Finally, we employ a dynamic evidential fusion strategy to adaptively integrate the multi-view evidence based on their respective quantified …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2608.25235
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.