← Latest papers
💻 computer science

Privacy-Utility Tradeoffs in Hierarchical Federated Learning Under Combined Differential Privacy and CKKS Homomorphic Encryption for Distributed Healthcare Networks

This paper proposes a hierarchical federated learning framework for healthcare that integrates client-level differential privacy with institution-level CKKS homomorphic encryption, demonstrating that while differential privacy incurs measurable accuracy losses dependent on the privacy budget, homomorphic encryption introduces no utility degradation, thereby isolating and quantifying the distinct privacy-utility tradeoffs of each mechanism.

Original authors: Sayed Mohammed Alwedaei, Jenan Moosa

Published 2026-07-09
📖 4 min read☕ Coffee break read

Original authors: Sayed Mohammed Alwedaei, Jenan Moosa

Original paper licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine a group of hospitals trying to build a super-smart medical AI together. They want to learn from their combined data to diagnose diseases better, but they have a strict rule: no hospital can ever see another hospital's raw patient data. It's like trying to bake a giant cake together, but no one is allowed to show their secret family recipe or even their bowl of ingredients to the others.

This paper is about a new "recipe" for how these hospitals can collaborate safely. The authors, Sayed Mohammed Alwedaei and Jenan Moosa, created a system called Hierarchical Federated Learning (HFL). Think of it as a three-story office building:

  1. The Clients (Ground Floor): Individual doctors or clinics with their own patient data.
  2. The Institutions (Middle Floor): The hospitals or large medical centers that manage the clinics.
  3. The Global Aggregator (Top Floor): The central AI brain that combines everything.

The Two Big Problems They Solved

The paper identifies two main ways privacy can be broken in this process:

  1. The "Leaky Bucket" Problem (Privacy): Even if you don't share the raw data, the "updates" (the lessons the AI learns) can sometimes reveal too much about the specific patients.
  2. The "Open Envelope" Problem (Confidentiality): Even if the updates are safe from leaking secrets, sending them over the internet is like sending a postcard. Anyone intercepting the mail can read it.

The Solution: A Double-Lock System

The authors combined two powerful tools to fix both problems at once:

1. Differential Privacy (The "Static Noise" Machine)
Imagine the doctors are trying to whisper a secret to the AI. To make sure no one can figure out exactly what they said, they add a little bit of "static noise" to their whisper.

  • How it works: Before sending their lesson, the system adds random mathematical noise. It's like turning up the volume on a radio just enough to drown out a specific voice, but keeping the overall song (the AI model) clear.
  • The Trade-off: The more noise you add (to be safer), the harder it is for the AI to learn the song perfectly. The paper tested different amounts of noise (called "privacy budgets" of 2, 4, 6, and 8).
    • Result: On a simple image task (MNIST), adding noise only made the AI slightly less accurate (about 1-2% drop). On a complex heart rhythm task (MIT-BIH), the drop was bigger (up to 12%), but still usable. The key finding: The noise is the only thing that makes the AI less accurate.

2. CKKS Homomorphic Encryption (The "Magic Envelope")
This is the second lock. Imagine sending your lesson inside a sealed, magical envelope that can be opened, read, and even added to other envelopes without ever being opened.

  • How it works: The hospitals encrypt their noisy updates. The middle-level hospitals (Institutions) can add these encrypted updates together mathematically without ever seeing the actual numbers inside. It's like a group of people adding up their bank balances on a locked calculator; the calculator gives the total, but no one sees the individual amounts.
  • The Surprise: The authors wanted to know: "Does this magic envelope slow down the AI or make it less smart?"
    • Result: Zero. The paper claims that using this encryption introduces no accuracy loss at all. The AI performs exactly as well with the encrypted data as it does with the noisy-but-unencrypted data.

The Big Takeaway

The most important discovery in this paper is the separation of costs.

  • Privacy Cost: Comes from the "noise" (Differential Privacy). It hurts accuracy a little bit, but keeps secrets safe.
  • Confidentiality Cost: Comes from the "encryption" (Homomorphic Encryption). It costs a little bit of time to lock and unlock the envelopes, but it does not hurt the accuracy of the AI at all.

The Verdict

The authors tested this on two datasets: handwritten digits (MNIST) and heart rhythm data (MIT-BIH). They found that:

  • You can have a very private system where the AI is still quite smart.
  • You can send these private updates over the internet securely (using the "magic envelope") without making the AI any dumber.
  • The system is stable; if you run the experiment three times, you get almost the exact same result every time.

In short, this paper proves that you can build a secure, collaborative medical AI where the "privacy" part makes it slightly less perfect, but the "security" part (keeping the data secret during transmission) doesn't cost you anything in terms of performance. It's a win-win for safety and speed.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →