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.
Glossary
Federated Communication Round

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.
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.
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.
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.
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.
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.
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.
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.
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.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Explore the core concepts that govern a single iteration of decentralized training, from client selection to secure aggregation.
Federated Client Selection
The strategic process of choosing a subset of available clients to participate in a specific communication round. Selection criteria often balance statistical heterogeneity with system constraints like bandwidth and device availability. Common strategies include random sampling, selecting clients with the most data, or prioritizing those with higher computational power to minimize straggler effects.
Federated Straggler Mitigation
Techniques to handle slow or unresponsive clients in synchronous training rounds. A straggler delays the entire aggregation process. Mitigation strategies include:
- Timeout-based dropping: Discarding updates from clients exceeding a deadline.
- Asynchronous protocols: Updating the global model immediately upon receiving any update.
- Coded computation: Using redundancy to reconstruct missing updates from faster clients.
Federated Model Divergence
The tendency of locally trained models to drift apart from the global optimum due to statistical heterogeneity in non-IID client data distributions. During a communication round, if local datasets are too dissimilar, the averaged global model may fail to perform well on any individual client's data. Proximal terms like those in the FedProx algorithm are often added to local objectives to constrain this drift.
Federated Parameter Server
The centralized or distributed infrastructure component responsible for storing the current global model and aggregating parameter updates received from participating clients at the end of each round. In a hub-and-spoke topology, this server acts as the single coordinator. In hierarchical federated learning, edge servers perform intermediate aggregation before sending updates to a central parameter server.
Federated Client Dropout
The phenomenon where selected clients fail to complete local training or return model updates within a communication round. This is common in cross-device FL due to connectivity issues, battery constraints, or user interruption. High dropout rates can introduce bias if the remaining clients are not representative of the full population, requiring robust aggregation algorithms.

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.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us