FedBCGD+: Federated Block Coordinate Descent
- FedBCGD+ is a family of federated learning methods that applies block-coordinate strategies, with one variant optimizing coupled global and personalized models and the other enhancing communication efficiency.
- The 2020 variant employs a quadratic penalty and hierarchical, asynchronous cloud-edge updates to balance personalization with global consensus and reduce latency.
- The 2026 variant partitions model parameters into blocks and incorporates client-drift control with SVRG corrections, significantly cutting communication costs while accelerating convergence.
Searching arXiv for the cited FedBCGD/FedBCGD+ papers and closely related terminology. arXiv search query: "FedBCGD+ federated block coordinate descent" FedBCGD+ is a name used in arXiv federated-learning literature for two distinct block-coordinate methods. In "Federated Block Coordinate Descent Scheme for Learning Global and Personalized Models" (Wu et al., 2020), FedBCGD⁺ denotes a federated block-coordinate-descent algorithm for joint learning of a global model and personalized local models under a quadratic penalty, together with a hierarchical cloud-to-edge and intra-cloud communication structure. In "FedBCD: Communication-Efficient Accelerated Block Coordinate Gradient Descent for Federated Learning" (Liu et al., 5 Mar 2026), FedBCGD+ denotes an accelerated communication-efficient method that partitions parameters into blocks, transmits only selected blocks, and augments client updates with client-drift control and stochastic variance reduction. The shared label reflects a common block-coordinate perspective, but the optimization objectives, communication models, and theoretical emphases differ substantially.
1. Terminology and problem setting
In the 2020 formulation, the central objective is personalization under federated privacy constraints. The method minimizes a coupled objective over a global model and client-specific models :
Here is the expected loss on device 's local distribution , is the global consensus model, is device 's personalized model, and is a regularization hyperparameter often called the personalization weight (Wu et al., 2020).
In the 2026 formulation, the central objective is communication efficiency for large-scale models such as Vision Transformer. The method splits model parameters into several blocks, including a shared block, and enables uploading a specific parameter block by each client. FedBCGD+ extends the basic FedBCGD framework with a client-drift control variate 0 and an SVRG-style variance-reduction correction (Liu et al., 5 Mar 2026).
A plausible implication is that the term "FedBCGD+" should not be treated as a single canonical algorithm without reference to its source paper. In the 2020 line, "plus" refers to momentum on the global model and an adaptive penalty schedule; in the 2026 line, "plus" refers to an accelerated block-coordinate scheme with client drift control and stochastic variance reduction (Wu et al., 2020, Liu et al., 5 Mar 2026).
2. Personalized FedBCGD⁺: joint global and local models
The 2020 method begins from a quadratic-penalty formulation that couples a global template to personalized client models. The penalty term 1 tethers each 2 to 3, so that learning is neither purely global nor fully decoupled (Wu et al., 2020). The paper states that by driving 4 one recovers pure personalization 5, whereas 6 decouples the clients and each solves its own problem. In practice, 7 is chosen to trade off global generalization against local tailoring (Wu et al., 2020).
The synchronous algorithm is organized as a two-step block-coordinate procedure. At communication round 8, the cloud broadcasts the current global model 9 to a subset 0 of participating clients. Each client 1 updates its local block while holding 2 fixed:
3
The implementation uses a single gradient step,
4
with step size 5 (Wu et al., 2020).
The cloud then updates the global block by solving
6
which yields the gradient-style update
7
where 8 (Wu et al., 2020). For the special choice 9, the update reduces to the model-averaging rule
0
This formulation makes block structure explicit at the level of optimization variables rather than parameter partitions. One block is the shared global template 1, and the other blocks are the personalized client models 2. This suggests that the method is aimed at statistically heterogeneous data settings in which a single fully shared model is not adequate.
3. Hierarchical communication and asynchronous cloud operation
A defining feature of the 2020 FedBCGD⁺ line is its two-layer communication structure: cloud-to-edge and intra-cloud among sub-cloud servers (Wu et al., 2020). In large-scale deployment, the cloud may itself be geographically distributed. The paper arranges cloud servers in a fast connectivity graph 3 and runs a lightweight consensus (gossip) or push-sum protocol.
The asynchronous procedure is described concretely. Whenever one server receives an updated 4 from edge 5, it incorporates it into its local sum, asynchronously exchanges partial sums with its neighbors in 6, and applies a local 7-update step of the same form as the synchronous global update but with the partially aggregated average (Wu et al., 2020). Under mild conditions—connected 8 and proper consensus weights—the stale aggregates converge to the true average exponentially fast in the intra-cloud iteration count.
The paper explicitly frames this asynchronous protocol as being inspired by multi-agent consensus technique and states that it has the potential for large gains in latency compared to a synchronous setting when the edge-device updates are intermittent (Wu et al., 2020). The significance of this design is not merely reduced idle time at slow clients. It also moves part of the aggregation burden into a distributed cloud layer, which is distinct from standard single-server federated averaging.
This architecture should not be conflated with the 2026 block-communication method. In the latter, block structure refers to partitioned parameter coordinates, and the server aggregates per-parameter-block updates in parallel. The 2026 paper does not describe the same hierarchical intra-cloud consensus mechanism (Liu et al., 5 Mar 2026).
4. Convergence properties of the personalization-oriented scheme
For the 2020 formulation, the composite objective is
9
The analysis assumes that each 0 is 1-smooth:
2
and that at each round only a random subset 3 of clients of average size 4 participates, with sampling independent across rounds (Wu et al., 2020).
The main convergence result is a sublinear stationarity guarantee. If the step sizes satisfy 5 and 6, then the iterates of synchronous FedBCGD satisfy
7
where
8
and 9 is the infimum of 0 (Wu et al., 2020). The paper states that, in particular, driving the expected squared norm of the block gradient below 1 requires 2 rounds.
The proof sketch proceeds through descent inequalities for each block update. For the local step,
3
A similar descent bound holds for the 4-update, and summation over rounds yields the stated rate (Wu et al., 2020). For the asynchronous cloud, a consensus-error term decaying as 5 per local gossip iteration, with 6, is added and absorbed into the same 7 rate once a fixed number of inner gossip steps is performed between each client-to-cloud round (Wu et al., 2020).
The theoretical message is therefore specific: the method provides nonconvex stationarity guarantees for personalized federated optimization with partial participation and an asynchronous cloud layer, rather than communication-complexity guarantees of the 8 type associated with parameter blocking.
5. Accelerated block-communication FedBCGD+: parameter partitioning, control variates, and SVRG
The 2026 FedBCGD+ addresses a different bottleneck: the high overhead expenses in each communication round for large-scale models such as Vision Transformer (Liu et al., 5 Mar 2026). The method splits model parameters into several blocks, including a shared block, and each client uploads a specific parameter block. The paper states that this is the first work on parameter block communication for training large-scale deep models (Liu et al., 5 Mar 2026).
The algorithmic structure is two-tiered. At the server, 9 clients are sampled and partitioned into 0 disjoint blocks 1 of size 2. The server broadcasts the global model 3 and global variate 4 to all selected clients (Liu et al., 5 Mar 2026). At the client side, for each block 5 and client 6, local updates take the form
7
This combines a minibatch stochastic gradient, a client-drift control term, and an SVRG-style correction (Liu et al., 5 Mar 2026).
The client-drift control variate is explicitly connected to SCAFFOLD. Each client 8 keeps 9, and the global control variate is
0
The server updates the blockwise control variates by
1
where 2 and 3 (Liu et al., 5 Mar 2026). The paper states that this ensures 4, so adding 5 corrects local drift.
The variance-reduction component is the zero-mean correction
6
motivated by the identity 7 (Liu et al., 5 Mar 2026). The local descent direction is summarized as
8
followed by 9 (Liu et al., 5 Mar 2026).
At the server, each block is aggregated in parallel:
0
followed by
1
The shared block 2 is aggregated similarly (Liu et al., 5 Mar 2026). Unlike the 2020 scheme, the block structure here is over parameter coordinates and explicitly targets reduction of transmitted floating-point values.
6. Rates and communication complexity in the block-communication line
The 2026 paper provides convergence theorems under smoothness and either strong convexity, general convexity, or non-convex assumptions. Let 3 denote the number of clients, 4 the number of sampled clients, 5, 6 the number of blocks, and define the effective server step 7 (Liu et al., 5 Mar 2026).
In the strongly convex case, if 8, then after 9 rounds,
0
and to reach 1 one needs
2
with communication cost
3
In the general convex case, under 4,
5
so 6-error takes
7
rounds and
8
In the non-convex case, if 9 and 00, then
01
so
02
and
03
The paper attributes the 04 improvement to the fact that only two blocks—the client's assigned block and a small shared block—of size 05 are sent per client, so the per-round cost is 06 instead of 07 (Liu et al., 5 Mar 2026). In the communication-complexity discussion, FedAvg and SCAFFOLD are described as sending a full 08-vector, namely 09 or 10 floats per client, whereas FedBCGD⁺ sends only two blocks out of 11, for a total of 12 floats per client (Liu et al., 5 Mar 2026).
The following comparison summarizes only quantities stated explicitly in the source material.
| Variant | Core objective | Communication emphasis |
|---|---|---|
| FedBCGD⁺ in (Wu et al., 2020) | Learn a global model 13 and personalized models 14 via a quadratic penalty | Hierarchical cloud↔edge and intra-cloud protocols, including sync and async settings |
| FedBCGD+ in (Liu et al., 5 Mar 2026) | Communication-efficient training via parameter blocks, client-drift control, and SVRG-style correction | Per-round upload of 15 floats and communication complexity lower by a factor 16 |
A plausible implication is that the two papers use the same label to denote different optimizations of the federated-learning stack: one emphasizes personalization and latency under hierarchical coordination, while the other emphasizes parameter-block communication efficiency for large models.
7. Empirical findings and relation to neighboring methods
The 2020 paper reports that FedBCGD⁺ combines momentum on 17 and adaptive penalty 18. The momentum update is
19
with 20, and the adaptive penalty increases 21 from 22 in early rounds to 23 by a geometric schedule (Wu et al., 2020). The paper states that the momentum term often cuts the required communication rounds by 20–30%. On the CIFAR-10 non-IID partition, FedBCGD⁺ achieves 70% accuracy in just 25 rounds, versus approximately 60 rounds for FedAvg, and attains a final personalization accuracy of 83.2%, versus 80.5% for FedAvg (Wu et al., 2020). On EMNIST, Table 2 is described as confirming that FedBCGD⁺ requires 40% fewer rounds to reach 99% personalized-accuracy than any previous method (Wu et al., 2020).
The 2026 paper reports experiments across CIFAR-10, CIFAR-100, Tiny-ImageNet, and EMNIST, and on architectures from LeNet-5 up to ViT-Base (Liu et al., 5 Mar 2026). It states that FedBCGD⁺ and its simpler FedBCGD variant reduce uplink by a factor of 24, accelerate convergence by approximately 25–26 versus FedAvg and SCAFFOLD, and match or improve final accuracy under non-IID splits (Liu et al., 5 Mar 2026). In the excerpt from Table 2, for LeNet-5 on CIFAR-100 with 100 clients, 27, and total budget 28, FedAvg reaches 40% test accuracy in 29 of upload, while FedBCGD⁺ reaches the same 40% in only 30 (Liu et al., 5 Mar 2026). In the excerpt from Table 5, for ViT-Base on Tiny ImageNet with 31 and 6 blocks, FedAvg needs 32 to hit 70% accuracy, FedBCGD achieves 83.5% in 33, and FedBCGD⁺ hits 81.3% in 34 (Liu et al., 5 Mar 2026).
The neighboring baselines mentioned explicitly are FedAvg, SCAFFOLD, and, in the 2020 paper, the state of the art for personalized models on edge devices (Wu et al., 2020, Liu et al., 5 Mar 2026). A common misconception would be to treat FedBCGD⁺ as a single method directly comparable across all these reported metrics. The source material indicates instead that the 2020 and 2026 versions solve different problems and report different types of gains. One emphasizes faster convergence for personalized models and latency reduction under asynchronous cloud aggregation; the other emphasizes reduced communication overhead through parameter-block transmission and accelerated convergence in terms of total transmitted floats (Wu et al., 2020, Liu et al., 5 Mar 2026).
Taken together, the two uses of FedBCGD+ define a small but technically heterogeneous family of federated block-coordinate methods. One branch is anchored in the optimization of coupled global and personalized models with a quadratic penalty and hierarchical communication. The other is anchored in blockwise parameter communication, server momentum, client-drift control, and SVRG-style local correction. Their commonality lies in block-coordinate structure; their divergence lies in what constitutes a block, which bottleneck is being optimized, and which convergence and efficiency criteria are foregrounded.