Inferensys

Glossary

Federated Communication Round

A single iteration in federated training consisting of local model training on selected clients followed by the transmission and aggregation of their updates.
ML engineer managing model training cluster on laptop, GPU utilization visible, technical deep learning setup.
DECENTRALIZED TRAINING ITERATION

What is a Federated Communication Round?

A single iteration in federated training consisting of local model training on selected clients followed by the transmission and aggregation of their updates.

A federated communication round is the fundamental iterative unit of federated learning where a central server distributes the current global model to selected clients, each performs local training on its private data, and the resulting model updates are transmitted back for aggregation. This cycle preserves data locality while enabling collaborative model improvement across decentralized nodes.

Each round begins with federated client selection, proceeds through parallel local optimization on heterogeneous federated data shards, and concludes with a federated aggregation algorithm such as FedAvg merging the updates. The efficiency of communication rounds is critical in cross-silo healthcare deployments, where minimizing round count directly reduces network overhead and accelerates convergence on sensitive clinical data.

Federated Training Lifecycle

Key Characteristics of Communication Rounds

A communication round is the fundamental atomic unit of federated training, orchestrating local computation and global aggregation. The following characteristics define its efficiency, security, and convergence behavior.

01

Client Selection

The strategic process of choosing a subset of available nodes to participate in a round. Random selection provides unbiased sampling, while greedy selection prioritizes clients with better connectivity or compute. In healthcare cross-silo settings, selection is often fixed due to institutional agreements. Poor selection strategies can introduce statistical bias or cause straggler delays.

5-100
Typical Clients per Round
02

Local Training & Compute

Selected clients download the global model and train locally on their private data shards. Key parameters include local epochs (passes over local data) and batch size. In synchronous rounds, all clients must complete this phase before aggregation. This step enforces data locality, ensuring raw PHI never leaves the hospital's infrastructure.

1-10
Typical Local Epochs
03

Gradient Transmission

Clients transmit only model updates (gradients or weights) to the aggregation server, not raw data. To reduce bandwidth, techniques like gradient compression (sparsification or quantization) are applied. In secure aggregation protocols, these updates are encrypted or masked so the server can only compute the sum, not inspect individual hospital contributions.

< 100 MB
Typical Update Payload
04

Aggregation & Convergence

The server merges client updates using algorithms like Federated Averaging (FedAvg). The global model is updated and redistributed for the next round. Convergence is measured by the stabilization of the global loss function. In non-IID healthcare data, aggressive aggregation can lead to model divergence, requiring proximal terms or personalized FL strategies.

100-1000+
Rounds to Convergence
06

Dropout & Fault Tolerance

Client dropout occurs when a node fails to return updates due to connectivity loss or resource preemption. Robust rounds implement timeout thresholds and straggler mitigation (e.g., ignoring late updates or using backup workers). In regulated healthcare environments, excessive dropout can invalidate a training run, requiring checkpointing and resumption protocols.

COMMUNICATION ROUND ESSENTIALS

Frequently Asked Questions

Clear answers to the most common questions about the mechanics, timing, and optimization of federated communication rounds in healthcare AI networks.

A federated communication round is a single complete iteration in the decentralized training lifecycle where selected clients perform local model training and transmit their updates for aggregation. The round begins when the federated parameter server distributes the current global model to a chosen subset of participating nodes. Each client then trains the model on its local federated data shard for a specified number of epochs, computing parameter updates (gradients or weights). These updates are encrypted and transmitted back to the server, where a federated aggregation algorithm such as Federated Averaging (FedAvg) combines them into a new global model. The round concludes when this updated model is ready for the next iteration. In healthcare cross-silo deployments, a single round may take minutes to hours depending on dataset sizes and computational resources at each hospital.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.