Inferensys

Glossary

Split Learning

A privacy-preserving collaborative learning technique where a deep neural network is partitioned between a client and a server, with the client transmitting only intermediate activations, not raw data or gradients.
Data scientist building training data pipeline on laptop, data preprocessing visible, technical workspace.
PRIVACY-PRESERVING DISTRIBUTED TRAINING

What is Split Learning?

A collaborative machine learning technique where a deep neural network is partitioned between a client and a server, with the client transmitting only intermediate activations rather than raw data or gradients.

Split Learning is a distributed machine learning paradigm where a deep neural network is physically partitioned into two segments: a client-side portion and a server-side portion. During training, the client processes raw data through its initial layers and transmits only the smashed data—the intermediate activations at the cut layer—to the server, which completes the forward pass, computes the loss, and backpropagates gradients to the cut layer before returning them to the client.

Unlike Federated Learning, where clients compute full model gradients locally, Split Learning ensures that the server never accesses raw training data or complete model parameters. This architecture is particularly advantageous in Cross-Silo Federated Learning for medical imaging, where resource-constrained hospital edge devices can offload compute-intensive layers to a central server while maintaining strict Data Residency compliance and mitigating Model Inversion Attack risks.

PRIVACY-PRESERVING COLLABORATIVE TRAINING

Key Features of Split Learning

Split Learning partitions a deep neural network between a client and a server, enabling collaborative training without exposing raw data. Only intermediate activations—not gradients or private inputs—are transmitted, providing a fundamentally different privacy paradigm from federated learning.

01

Network Partitioning Architecture

The neural network is physically divided into two segments: a client-side portion that remains on the data-holding institution's infrastructure, and a server-side portion hosted remotely. The client computes forward passes up to a designated cut layer, then transmits only the resulting smashed data (intermediate activations) to the server. The server completes the forward pass, computes the loss, and backpropagates gradients to the cut layer. Crucially, the server never accesses raw input data or full model gradients, fundamentally limiting information leakage compared to federated averaging approaches.

Zero
Raw Data Transmitted
Cut Layer
Privacy Boundary
02

U-Shaped Training Protocol

Split learning employs a sequential, U-shaped communication pattern rather than parallel client updates. The process flows:

  • Forward Pass: Client computes to cut layer → transmits activations → server completes forward pass
  • Backward Pass: Server computes gradients to cut layer → transmits gradients back → client completes backpropagation This sequential nature eliminates the need for clients to share model weights, but introduces communication latency as a primary engineering consideration. The protocol is particularly suited for cross-silo settings where institutions have reliable, high-bandwidth connections.
Sequential
Communication Pattern
2
Transmissions per Batch
03

Label Privacy Protection

Unlike federated learning where labels may be inferred from gradient updates, split learning can be configured so that labels remain exclusively on the server side. In medical imaging contexts, this means the institution holding patient scans (the client) never needs to share diagnostic labels with external parties. The server computes the loss function without the client accessing label information, creating an asymmetric privacy guarantee. This architecture is valuable when labels themselves constitute protected health information or proprietary clinical annotations.

Server-Only
Label Visibility
04

SplitFed Hybrid Approaches

SplitFed combines the privacy properties of split learning with the parallel training efficiency of federated learning. Multiple clients maintain their own client-side network segments and train simultaneously, while a shared server-side network processes all smashed data. This hybrid architecture:

  • Reduces the idle time inherent in sequential split learning
  • Preserves the raw data privacy guarantees of the split architecture
  • Enables multi-institutional collaboration at scales impractical for pure split learning SplitFed is emerging as a practical compromise for healthcare consortia requiring both privacy and throughput.
Parallel
Client Training
Hybrid
Architecture Type
05

Cut Layer Selection Strategy

The choice of cut layer represents a critical design decision balancing privacy, communication efficiency, and model performance:

  • Shallow cut (early layers): More computation on server, smaller transmitted activations, but greater information leakage risk from low-level features
  • Deep cut (later layers): Stronger privacy guarantees as transmitted features are more abstract, but larger activation tensors increase bandwidth requirements
  • Optimal placement depends on the specific data modality, network architecture, and threat model. For medical imaging, deeper cuts are typically preferred to ensure transmitted representations cannot be inverted to reconstruct identifiable patient scans.
Privacy vs. Efficiency
Design Tradeoff
06

No Gradient Sharing Requirement

A fundamental distinction from federated learning: split learning clients never transmit model gradients to any external party. Only intermediate activations flow from client to server, and only gradients up to the cut layer flow back. This eliminates entire classes of gradient leakage attacks that can reconstruct training data from shared weight updates. The server learns only the representation at the cut layer, not the parameters or gradients of the client-side network. This property makes split learning particularly compelling for regulatory compliance under GDPR and HIPAA frameworks where gradient sharing may be considered a data transfer.

None
Gradients Shared
Activations Only
Client Output
PRIVACY-PRESERVING TECHNIQUE COMPARISON

Split Learning vs. Federated Learning vs. SMPC

A comparison of three distinct privacy-preserving collaborative learning and computation paradigms for multi-institutional medical imaging.

FeatureSplit LearningFederated LearningSecure Multi-Party Computation

Core Mechanism

Neural network partitioned between client and server; only intermediate activations (smashed data) are transmitted

Model weights trained locally; only weight updates (gradients) are transmitted to an aggregation server

Cryptographic protocol enabling joint computation over private inputs without revealing individual inputs

Data Transmitted

Intermediate activations and gradients of the cut layer

Model weight updates or gradients

Encrypted secret shares of private inputs

Raw Data Exposure

Model Architecture Access

Server never sees the full model; client holds initial layers, server holds remaining layers

All clients and the server share the identical global model architecture

Not applicable; computation is performed on encrypted shares, not a shared model

Computational Overhead

Moderate; sequential forward and backward passes across the network boundary

Low to Moderate; parallel local training with periodic communication rounds

Very High; orders of magnitude slower than plaintext computation due to cryptographic operations

Communication Pattern

Sequential, per-batch communication between client and server during training

Synchronous or asynchronous rounds of weight update aggregation

Multiple rounds of message exchange between all participating parties for each operation

Primary Use Case

Training deep models where clients lack resources for full local training or cannot share the model architecture

Training a shared global model across many decentralized data silos

Computing a specific function (e.g., statistical query, inference) over combined private datasets

Label Requirement

Labels can reside on the server side, eliminating the need for labeled data on the client

Labels must reside on the client with the corresponding training data

Labels are a private input from one or more parties

SPLIT LEARNING CLARIFIED

Frequently Asked Questions

Concise answers to the most common technical and strategic questions about implementing split learning for privacy-preserving medical imaging.

Split learning is a privacy-preserving collaborative learning technique where a deep neural network is partitioned between a client and a server, with the client transmitting only intermediate activations (smashed data), not raw data or gradients. In a medical imaging context, a hospital (client) holds the initial layers of a convolutional neural network and processes a chest X-ray locally. The output—a compressed, obfuscated feature map—is sent to a central server that completes the forward pass through the remaining layers. The server computes the loss and backpropagates gradients only through its own layers, then sends the gradient of the activations back to the client to update its local layers. This cut layer architecture ensures raw patient scans never leave the institution, satisfying data residency requirements while enabling collaborative diagnostic model training.

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.