---
title: Federated Split Learning (FedSL)
url: https://www.emergentmind.com/topics/federated-split-learning-fedsl
type: topic
---

# Federated Split Learning (FedSL)

Federated Split Learning (FedSL), also written as SFL in several papers, is a hybrid distributed-learning paradigm that combines Federated Learning (FL)’s parallel client-side training with Split Learning (SL)’s partitioning of a deep model into a client-side subnetwork and a server-side subnetwork. In its standard form, the full model is split at a cut layer, clients compute forward activations on local data, the server completes the forward and backward passes on the remaining layers, and a federated aggregation step synchronizes the client-side submodels. This design is used to reduce client computation relative to FL, avoid SL’s sequential-relay bottleneck, and keep raw data local, while introducing new trade-offs in communication, privacy leakage through smashed data, server storage, and cut-layer selection [2311.09441][2004.12088].

## 1. Conceptual foundations and historical development

FedSL emerged from the limitations of FL and SL when considered in isolation. FL requires each client to store and train the full model, which becomes impractical for large DNNs and resource-constrained devices. SL reduces client-side compute by assigning only an early network portion to the client, but classical SL is sequential and therefore incurs long end-to-end delay as the number of clients grows. SplitFed Learning was introduced specifically to amalgamate the two approaches, retaining SL’s split-model privacy and resource relief while recovering FL-style parallelism [2004.12088][2011.14818].

A common formalization writes the full model as
\[
W=\bigl[\,W_C;\;W_S\bigr], \qquad |W_C|=\alpha |W|,\;\; |W_S|=(1-\alpha)|W|,\;\; \alpha\in[0,1],
\]
where \(W_C\) denotes the client-side submodel and \(W_S\) the server-side submodel. In another equivalent notation used for industrial settings,
\[
M(x;\theta)=B(A(x;\theta_A);\theta_B),
\]
with \(A\) the device-side submodel and \(B\) the server-side remainder [2311.09441][2510.05713].

The literature does not treat FedSL as a single fixed protocol. Instead, it defines a family of architectures. Some papers use a main server for server-side training and a separate fed server for aggregation of client-side weights [2004.12088][2011.14818]. Others use paired edge servers with periodic aggregation of server-side weights only [2301.01824]. Still others generalize the same idea to wireless edge networks, vehicular edge computing, GANs, RNNs over sequentially partitioned data, and decentralized blockchain-managed deployments [2310.15584][2207.01750][2011.03180][2507.07637].

## 2. Canonical architecture and training protocols

A typical FedSL training round has three phases. First, each client runs a forward pass on a local mini-batch through \(W_C\), producing smashed data \(z\). Second, the server receives \(z\), continues the forward pass through \(W_S\), computes the loss, backpropagates through \(W_S\), and returns \(\nabla_z\) to the client. Third, the client completes backpropagation through \(W_C\), updates its local copy of \(W_C\), and uploads its updated client-side parameters to a federated aggregator, which applies FedAvg to \(\{W_C^{(k)}\}_{k=1}^K\) and broadcasts the new global \(W_C\) [2311.09441].

In the original SplitFed configuration, clients hold identical client-side subnetworks \(W_k^{\rm C}\), the main server holds \(W^{\rm S}\), and the fed server aggregates client-side updates by weighted averaging,
\[
W^{\rm C}_{t+1}=W^{\rm C}_t-\eta \sum_{k=1}^K \frac{n_k}{n}\,\tilde g_k,
\]
while the main server computes losses on smashed activations and returns cut-layer gradients \(\delta A_k\) for client-side backpropagation [2004.12088]. The chapter treatment of SplitFed emphasizes that clients operate in parallel, whereas vanilla SL trains clients sequentially [2011.14818].

Not all FedSL systems aggregate the same model portion. In the hybrid architecture of [2301.01824], client–server pairs train locally on split models, but only the server-side weights are periodically averaged through “SerAVG,” while clients do not share or average their local \(W^{(1:c)}\). That design preserves the split-learning training flow yet changes the synchronization locus from client-side to server-side [2301.01824].

Several specialized protocols adapt the same template to different model classes. FedSL-GAN places the Generator \(G\) on the server and splits the Discriminator \(D\) vertically across a client’s resource-constrained devices; clients collaboratively evaluate the split discriminator on both local real data and generated samples, then the server performs FedAvg over discriminator updates and updates \(G\) using discriminator feedback [2207.01750]. For sequentially partitioned data, the RNN-based FedSL framework distributes consecutive sequence segments across clients, exchanges hidden states \(h_{\tau_i}\) and split gradients \(\delta_i\) between neighboring clients, and aggregates the segment-specific sub-networks on a server; this protocol is tailored specifically to cases where neither standard FL nor cut-layer SL can handle the temporal partitioning [2011.03180].

## 3. Optimization of split points, bandwidth, and system resources

A central technical issue in FedSL is the choice of cut layer or split point. In wireless settings, the split point simultaneously determines client compute, smashed-data size, and communication latency. One formulation considers \(K\) heterogeneous edge devices and one server, with device-specific split points \(s_k\in\{1,\dots,L\}\), bandwidth ratios \(b_k\in[0,1]\), and per-iteration latency dominated by the slowest device:
\[
\mathbb E[\tau^{\rm total}]
=
\mathbb E\!\left[\max_{k=1\dots K}\bigl(\tau^{cp}_{s_k}+\tau^{cm}_{s_k}(b_k)\bigr)\right].
\]
The corresponding optimization minimizes expected latency subject to split-point feasibility and bandwidth constraints, with an accuracy condition
\[
(1-1/K)\,s_k\,\Phi^2 \le \hat \Phi^2.
\]
The proposed solution alternates between split-point optimization and bandwidth allocation, yielding a complexity
\[
O(N_{\rm iter}\cdot K\cdot \hat \ell + N_{\rm iter}\cdot K\cdot \log(1/\epsilon))
\]
and a closed-form bandwidth update
\[
b_k^*=
\frac{D_{s_k^*}}{W\log_2(1+\gamma_k)\,(T^*-\tau^{cp}_{s_k^*})}
\]
with \(T^*\) found by binary search [2310.15584].

Later heterogeneous FedSL formulations make the split point client-specific by design. HSFL allows each client \(k\) to choose its own cut-layer index \(\ell_k\), producing personalized client-side \(W_k^c\) and server-side \(W_k^s\), and jointly optimizes cut layers, main-server CPU allocation, and bandwidth. The long-timescale problem selects \(\ell_k\) by Sample Average Approximation and a Genetic Algorithm, while the short-timescale problem uses Lagrangian relaxation for CPU allocation and Branch and Bound for bandwidth allocation [2411.13907].

Vehicular edge computing adds mobility and deadline constraints to the same problem class. ASFV assigns a cut-layer \(\epsilon_n^t\) to each participating vehicle at round \(t\), selects only vehicles whose per-round delay satisfies the sojourn-time constraint, and jointly optimizes cut layers, uplink powers, CPU frequencies, and OFDMA bandwidth ratios by block coordinate descent over three subproblems [2405.18707].

A more recent wireless-edge formulation expands the decision space still further. TiLP jointly chooses bandwidth, transmit power, split-layer placement, compression level, and terminal participation under per-round deadline, memory, spectrum, and energy constraints, and evaluates candidate actions through a cross-domain digital twin comprising network, training, and task sub-twins [2604.26105]. This suggests that, in modern FedSL systems, split-layer placement is increasingly treated as one decision variable within a larger mixed continuous-discrete resource-allocation problem rather than as an isolated architectural choice.

## 4. Privacy, communication, storage, and reliability trade-offs

FedSL preserves privacy in the limited sense that raw data remain local, but the main privacy concern is an honest-but-curious server attempting to reconstruct inputs from smashed data. One formal treatment measures reconstruction success by the Structural Similarity Index (SSIM) and defines
\[
RS(\alpha)=\mathbb E[\mathrm{SSIM}(x,\hat x(\alpha))].
\]
In the reported experiments, deeper cut layers produce more non-linear compression and lower \(RS(\alpha)\), while the client energy
\[
E(\alpha)=g_e\Bigl(l_e\,D_b\,E_{\text{main}(\alpha)}+E_{\text{fed}(\alpha)}\Bigr)
\]
increases with \(\alpha\). The resulting privacy–energy trade-off is posed as
\[
\min_{\alpha} RS(\alpha)
\quad \text{s.t.}\quad
E(\alpha)\le E_{\rm req},
\]
with a Fashion-MNIST example yielding \(\alpha^*=0.4201\) [2311.09441].

Communication remains a major bottleneck because standard FedSL transmits smashed data and cut-layer gradients in every round. CSE-FSL addresses this by attaching an auxiliary network to the client-side cut layer so that clients can update their local models without waiting for server-side gradients, keeping only a single model at the server and uploading smashed data only every \(h\) client mini-batches. Under standard assumptions, the method guarantees
\[
\frac1T\sum_{t=0}^{T-1}\mathbb E\|\nabla F(\theta^t)\|^2
=
O(1/\sqrt T)+O(\Delta^2)
\]
for non-convex objectives [2302.05599]. A later presentation of the same line of work states client-side and server-side convergence rates of order \(O(1/\sqrt T)\) under \(L\)-smoothness, bounded variance, and bounded drift, while making explicit that server storage becomes independent of the number of clients because only a single server submodel is maintained [2507.15816].

FSL-SAGE targets the same communication bottleneck from a different angle. Each client maintains an auxiliary model \(\mathbf x_{a,i}\) that estimates the server-side gradient with respect to smashed activations, and the server aligns this auxiliary only once every \(l\) rounds. The resulting total communication is
\[
O\bigl(T\,Qd_z + \tfrac{T}{l}d_a\bigr),
\]
with convergence
\[
\min_{0\le t<T}\mathbb E\|\nabla f(\mathbf x^t)\|^2
=
O(1/\sqrt T)+\frac1T\sum_{t=0}^{T-1}\varepsilon_\star^t
\]
and recovery of \(O(1/\sqrt T)\) stationarity when the auxiliary class is sufficiently expressive [2505.23182].

Additional system-level modifications target compute and transmission reduction directly. A lightweight wireless FedSL scheme prunes the client-side model dynamically using a first-order Taylor criterion, quantizes gradients with \(q\)-bit stochastic rounding, and applies random dropout to split-layer activations. Its main convergence theorem bounds the average squared-gradient norm after \(T\) rounds under \(\beta\)-smoothness, bounded variance, pruning error, and quantization error assumptions [2412.06414].

Privacy and efficiency objectives do not always align with robustness. Under packet loss at the split point, experiments on embryo image segmentation showed a statistically significant advantage of a deeper split point: deep split consistently outperformed shallow split across all tested \((P_L,N_c)\) combinations, although deeper splits also increase client-side computation [2405.19453]. This directly counters the common misconception that “raw data never leave the device” is by itself a complete privacy or reliability characterization. In FedSL, smashed data can remain reconstructible, shallow cuts can raise leakage risk, and communication errors can alter the effective optimal cut point [2311.09441][2405.19453].

## 5. Major variants and application domains

FedSL has diversified into several task-specific and deployment-specific variants. The same core design—split execution plus federated synchronization—has been adapted to adversarial generation, sequential modeling, vehicular edge intelligence, wireless edge robotics, pre-trained Transformer backbones, computing power networks, industrial IoT, and decentralized blockchain control [2207.01750][2011.03180][2405.18707][2604.26105][2403.16050][2305.12979][2510.05713][2507.07637].

| Variant | Defining feature | Representative domain |
|---|---|---|
| FedSL-GAN | Generator on server, split Discriminator across client devices | MNIST/DCGAN |
| Sequential-data FedSL | Hidden-state and split-gradient exchange across sequence segments | Sequential MNIST, eICU |
| ASFV | Adaptive cut-layer, vehicle selection, and radio/CPU allocation | Vehicular edge computing |
| FedV / FedVZ | Pre-trained Image Transformer encoder; zeroth-order server update in FedVZ | CIFAR-10, CIFAR-100, Tiny-ImageNet |
| CPN-FedSL | Client admission, split-layer choice, server placement, routing, and bandwidth allocation | Computing Power Network |
| HLF-FSL | Hyperledger Fabric chaincode orchestrates split execution and peer-to-peer aggregation | Enterprise IoT |

FedSL-GAN uses the inherent privacy-preserving attribute of GANs: the server trains the Generator \(G\) without ever seeing real private data, while the split Discriminator \(D\) is trained collaboratively on client devices with only activations, discriminator parameters, and gradient feedback traversing the network [2207.01750]. The sequential-data framework for RNNs is notable because it handles “sequential partitioning,” where consecutive sequence segments reside on different clients, and communicates only hidden states and split-layer gradients rather than raw segments, labels, or full model parameters [2011.03180].

FedV and FedVZ extend FedSL to pre-trained image Transformers. FedV initializes the server-side encoder with a public-data pre-trained image Transformer, while FedVZ replaces the exact server gradient with a zeroth-order approximation based on two forward evaluations, explicitly to hinder gradient inversion attacks in black-box scenarios [2403.16050]. CPN-FedSL treats FedSL as a scheduling service over a Computing Power Network and optimizes client admission, model partition, server selection, routing, and bandwidth allocation using a Resource Usage Effectiveness objective and the Refinery algorithm [2305.12979]. HLF-FSL removes the central coordinator by combining FedSL with Hyperledger Fabric, using transient fields for activations and gradients and Private Data Collections for hashes or off-chain references of large artifacts [2507.07637].

## 6. Empirical findings, limitations, and research directions

Across the literature, FedSL is repeatedly evaluated against FL, SL, and other FedSL variants on latency, communication, convergence speed, accuracy, and privacy-related criteria. In heterogeneous wireless training, joint split-point and bandwidth optimization yielded up to 75% latency reduction on VGG16 and 60–70% on AlexNet relative to FedAvg, while reaching target accuracy in approximately 40–60% of the time required by FedAvg under both IID and non-IID settings; the same study reported that enlarging the split-point constraint \(\hat \ell\) improves latency but degrades final accuracy by up to 2–3% [2310.15584]. HSFL was reported to converge 30% faster than SplitFed and 50% faster than FL on HAM10000, with the joint optimization algorithm reducing latency by up to 40% versus RCLS and 25% versus SCLS [2411.13907].

Communication- and storage-oriented variants report different gains. CSE-FSL achieved communication savings up to approximately 94% versus FSL_MC and reduced server storage by approximately 70% versus FSL_AN, while maintaining comparable or better accuracy than baselines on CIFAR-10 and F-EMNIST [2302.05599]. FSL-SAGE reached 85.7% on homogeneous CIFAR-10 at only 80 GiB, compared with approximately 84% for SplitFedv1 and CSE-FSL at approximately 200 GiB, and remained robust under extreme non-IID conditions where FedAvg and SplitFedv2 failed to converge within 200 GiB [2505.23182]. In FedSL-GAN, the overall epoch time on the slowest client was reduced by up to 40% compared to pure FL on the weakest device [2207.01750].

Application-specific evaluations show similarly task-dependent benefits. In vehicular edge computing, ASFV achieved test accuracy of approximately 80% on CIFAR-10 non-IID in 30 rounds versus approximately 65% for FL at the same round, with per-round delay of approximately 6 s compared to approximately 9 s for SFL4, approximately 11 s for FL, and approximately 16 s for SL at \(N=25\) vehicles [2405.18707]. In blockchain-based deployment, HLF-FSL achieved 94.14% final CIFAR-10 test accuracy versus 94.7% for centralized FSL, while MNIST reached 99.43% and 98% by epoch 5 [2507.07637]. In wireless edge robotics, TiLP achieved 87.5% final task success, improving task success by 9.5 percentage points over the strongest baseline while satisfying the per-round deadline and energy budget [2604.26105].

The literature also converges on a set of unresolved problems. Dynamic split selection under time-varying compute and channel conditions is repeatedly identified as an extension of fixed-cut FedSL [2310.15584][2311.09441]. Extending convergence guarantees from strongly convex settings to non-convex DNNs remains open in wireless formulations [2310.15584]. Other recurring directions include multi-server and hierarchical splitting, robust aggregation under non-IID data and stragglers, privacy defenses beyond reconstruction attacks, model compression, quantization, and joint optimization of communication, computation, and cut-layer placement [2311.09441][2411.13907][2510.05713].

Taken together, these results indicate that FedSL is best understood not as a single algorithm but as a design space. Its core mechanism—parallel split execution with federated synchronization—supports substantial reductions in client compute and, in many settings, wall-clock training time. At the same time, the choice of cut layer, synchronization rule, auxiliary models, aggregation locus, and network orchestration determines whether the dominant bottleneck is communication, privacy leakage, server storage, or deadline feasibility. That plurality of formulations is now a defining characteristic of the field [2311.09441][2510.05713].

Source: https://www.emergentmind.com/topics/federated-split-learning-fedsl