Inferensys

Glossary

Communication Round

A single complete cycle in federated training consisting of the server distributing the current global model, selected clients performing local training, and the server aggregating the resulting weight updates.
ML engineer managing model training cluster on laptop, GPU utilization visible, technical deep learning setup.
FEDERATED LEARNING CYCLE

What is a Communication Round?

A single complete iteration in federated training where the server distributes the global model, selected clients perform local training, and the server aggregates the resulting weight updates.

A communication round is the fundamental iterative cycle in a federated learning process. It begins when the central aggregation server transmits the current global model parameters to a selected cohort of participating client nodes. Each client then performs local training on its private, on-device dataset—such as a hospital's radiology archive—to compute a model update, typically in the form of weight gradients, without exposing any raw patient data.

The round concludes when the server collects these encrypted or differentially private updates from the clients and executes an aggregation algorithm, most commonly Federated Averaging (FedAvg), to produce a new, improved global model. This cycle repeats for many rounds until the model converges, with each round representing a single step of collaborative learning across the decentralized network.

COMMUNICATION ROUND CLARIFIED

Frequently Asked Questions

Clear, technically precise answers to the most common questions about the communication round—the fundamental iterative cycle that powers federated learning across distributed medical institutions.

A communication round is a single complete cycle in federated training consisting of three sequential phases: the server distributes the current global model to selected client nodes, those clients perform local training on their private data, and the server aggregates the resulting weight updates to produce an improved global model. This cycle repeats for hundreds or thousands of rounds until the model converges. Each round represents one atomic unit of collaborative learning where raw data never leaves its source institution, only encrypted or compressed model updates are transmitted. The term 'communication round' specifically refers to the network I/O and synchronization event, distinguishing it from purely local computation epochs.

Federated Learning Lifecycle

Key Characteristics of a Communication Round

A communication round is the fundamental iterative cycle in federated training. It defines how a global model is distributed, locally improved, and securely aggregated without centralizing raw data.

01

Server-to-Client Distribution

The round begins with the aggregation server broadcasting the current global model weights to a selected subset of participating client nodes. This step ensures all clients start local training from a synchronized state. The selection strategy can be random or based on specific eligibility criteria like device charging status or network connectivity.

02

Local Model Training

Each selected client performs stochastic gradient descent (SGD) on its private, local dataset for a fixed number of epochs. This step generates a set of weight updates (gradients) that capture the unique statistical patterns of the local data without exposing the raw data itself. The computational burden is distributed, preserving data locality.

03

Secure Update Transmission

Clients encrypt their computed weight updates using protocols like Secure Aggregation (SecAgg) or Differential Privacy (DP) before transmission. This cryptographic layer ensures the central server cannot inspect any single institution's contribution in plaintext, mitigating the risk of model inversion attacks and maintaining strict regulatory compliance.

04

Aggregation and Global Update

The server collects the encrypted updates and applies an aggregation algorithm, most commonly Federated Averaging (FedAvg). It computes a weighted average of the updates to produce a new, improved global model. Robust aggregation variants like Krum can be used to defend against Byzantine failures or poisoned updates.

05

Convergence and Iteration

The cycle repeats for hundreds or thousands of rounds until the global model's performance converges to a satisfactory accuracy threshold. The total number of rounds required is heavily influenced by the degree of statistical heterogeneity (Non-IID data) across the client silos, with more heterogeneous data often requiring more communication rounds.

06

Communication Efficiency Constraints

A critical bottleneck in this cycle is the bandwidth required to transmit large model weights. Techniques like gradient compression (sparsification and quantization) and Federated Distillation are often applied to reduce the payload size, making the round viable for cross-device settings with limited network capacity.

Federated vs. Centralized Training Cycles

Communication Round vs. Centralized Training Epoch

A structural comparison of a single communication round in federated learning against a standard training epoch in a centralized data center, highlighting differences in data locality, privacy, and compute topology.

FeatureCommunication RoundCentralized Training Epoch

Data Locality

Data remains on distributed client nodes

Data pooled in a single data lake or warehouse

Primary Bottleneck

Network bandwidth and client heterogeneity

GPU compute throughput and I/O bandwidth

Privacy Guarantee

Raw data never leaves the source institution

Raw data is fully exposed to the training process

Compute Topology

Decentralized; parallel local updates on N clients

Centralized; single cluster or GPU pod

Update Mechanism

Server aggregates N distinct model weight deltas

Optimizer updates weights from a single global batch

Data Distribution

Non-IID across heterogeneous institutional silos

Shuffled IID distribution across homogeneous nodes

Regulatory Alignment

Compliant with data residency and HIPAA constraints

Requires complex Data Use Agreements for PHI

Failure Mode

Straggler clients or Byzantine node poisoning

Single point of hardware failure or data corruption

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.