Skip to content
Enrique Tomás Martínez Beltrán
HomeResearchPublicationsTopicsTeachingBlog
Contact
EN/ES
HomeResearchPublicationsTopicsTeachingBlogContact
EN/ES

Enrique Tomás Martínez Beltrán

Postdoctoral research in AI, cybersecurity and federated learning, spanning threat analysis, closed-loop cyberdefense and trustworthy decentralized learning.

  • Privacy Policy
  • Terms of Service
  • Accessibility Statement
  • Google Scholaropens in a new tab
  • ORCIDopens in a new tab
  • LinkedInopens in a new tab
  • GitHubopens in a new tab
All profiles
  • ResearchGateopens in a new tab
  • Scopusopens in a new tab
  • DBLPopens in a new tab
  • Web of Scienceopens in a new tab

Enrique Tomás Martínez Beltrán. All rights reserved.

Back to top

This site loads optional analytics from Google and external analytics providers only if you accept. You can decline and continue using the site normally.

  1. Home
  2. Research Notes on Federated Learning, Cybersecurity and Cyberdefense
  3. From Survey to Prototype: A Research Workflow for DFL
Research MethodologyDecentralized Federated LearningCyberdefenseMultimodal Learning

From Survey to Prototype: A Research Workflow for DFL

How architectural mapping, threat scenarios and new mechanisms can form one research program

Enrique Tomás Martínez Beltrán

Postdoctoral Researcher in Computer Science

August 5, 20267 min read
  • LinkedInopens in a new tab
  • Xopens in a new tab
From Survey to Prototype: A Research Workflow for DFL

Research on decentralized federated learning benefits from a sequence that moves from map to mechanism to evidence. The doctoral thesis follows that logic: first it characterizes the field, then it tests reliability in a concrete operational scenario and finally it designs a protocol for heterogeneous multimodal clients.

This is more than a convenient chapter order. Each stage narrows a different uncertainty. A survey reveals which assumptions are repeated across the literature. A controlled system study shows how those assumptions behave under a threat model. A new learning mechanism tests whether the protocol can address a limitation that remains visible after the first two stages.

Stage 1: build the map

The survey publication organizes DFL around architectures, components, topologies, communication, security, privacy, optimization, frameworks and applications. It also asks how systems are evaluated. That map is valuable because terminology alone can hide different responsibilities: two papers may both say “decentralized” while using different neighbor rules, aggregation semantics or trust assumptions.

A useful output of this stage is a design matrix:

QuestionExamples of answers
Who communicates?peers, clusters or changing neighborhoods
What is shared?parameters, gradients, prototypes or statistics
How is influence decided?fixed weights, consensus or trust-aware rules
What can fail?links, clients, resources, labels or modalities
How is success measured?quality, cost, convergence and resilience

Stage 2: choose a demanding scenario

Flighter instantiates the reliability problem in a simulated military aerial-reconnaissance setting. Four SAR-equipped aircraft collaborate while their formation, position, interconnection behavior and resources become part of the context. The experiment uses VGG16 and MSTAR, SAMPLE and OpenSARShip to make the threat discussion measurable.

This stage is important because it prevents a robustness claim from remaining abstract. It forces the research to define indicators, normalize them, compare them with a dynamic threshold and decide what happens to a contribution whose evidence becomes weak. It also keeps a baseline without the extra situational-awareness mechanism.

Stage 3: address a different source of difficulty

The Modalis contribution moves from adversarial context to heterogeneous observations. Clients can have different class distributions and different or missing modalities. The protocol exchanges compact prototypes and adds contextual placeholders, adaptive gating, multimodal fusion and alignment objectives.

The datasets are deliberately varied: AVMNIST, CREMA-D, UCI-HAR and CRISIS-MMD. The main experiments use 20 clients on a specified Erdős-Rényi graph, with controlled class skew and missing-modality probabilities. This makes the comparison interpretable while leaving room for future work on dynamic topology and real deployments.

Why the sequence is useful

The stages share a vocabulary without forcing one solution onto every problem. The survey identifies design dimensions. Flighter shows that operational reliability can influence decentralized aggregation. Modalis shows that the exchanged object itself can be redesigned when full-model sharing is a poor fit for partial views.

The result is a research workflow that can be reused:

  1. map the design space and expose hidden assumptions;
  2. select one failure or heterogeneity mechanism;
  3. define an operationally meaningful scenario;
  4. implement the smallest mechanism that addresses the limitation;
  5. evaluate quality, cost, resources and failure behavior together;
  6. state the conditions under which the result should not be generalized.

Connecting the publications

The three constituent articles are available as a survey in IEEE Communications Surveys and Tutorials, the Flighter study in IEEE Communications Magazine and the Modalis study in Information Fusion. Reading them as a sequence makes the progression visible without treating the final mechanism as a universal answer.

The broader lesson is methodological. DFL research becomes more credible when architectural claims, threat assumptions, data heterogeneity and measurement choices are connected. A map without an experiment is too abstract. An experiment without a map can optimize the wrong problem. A mechanism without a clear boundary can be oversold.

This note is an original editorial synthesis of the thesis structure and its three publications. It is not a restatement of any article.

Related Research

From Monitoring to Mitigation: A DFL Cyberdefense Lifecycle with LLM Explanations

May 30, 2026

From Monitoring to Mitigation: A DFL Cyberdefense Lifecycle with LLM Explanations

A practical note on how distributed monitoring, DFL models, alert evidence and LLM-based support can fit into a cyberdefense workflow.

Situational Awareness for Cyberdefense with Decentralized Federated Learning

May 29, 2026

Situational Awareness for Cyberdefense with Decentralized Federated Learning

A research note on using DFL to turn distributed telemetry, anomalies and trust signals into cyberdefense situational awareness.