← Latest papers
🤖 machine learning

Multi-Level Analyzation of Imbalance to Resolve Non-IID-Ness in Federated Learning

This paper proposes FedBB, a federated learning framework that addresses data imbalance at inter-case, inter-class, and inter-client levels through a Positive Negative Balanced loss function and Client Balanced Reweighting strategy, thereby outperforming existing algorithms in accuracy and efficiency while preserving privacy.

Original authors: Haengbok Chung, Jae Sung Lee

Published 2026-06-10
📖 5 min read🧠 Deep dive

Original authors: Haengbok Chung, Jae Sung Lee

Original paper licensed under CC BY 4.0 (http://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 doctors from different hospitals trying to build a single, super-smart AI to diagnose diseases. They want to do this without sharing their actual patient files (to protect privacy), so they train their own local AI models and send just the "lessons learned" back to a central server to combine them. This is Federated Learning.

However, there's a big problem: The data is messy.

Some hospitals see mostly healthy patients, some see mostly sick ones, and some see a weird mix of rare diseases. In the paper, the authors call this "Non-IID" (data that isn't identical or evenly distributed). Because of this mess, the final combined AI often gets confused and performs poorly.

The authors of this paper, Haengbok Chung and Jae Sung Lee, say, "We need to look at this mess from three different angles." They call their solution FedBB (Federated Learning with Positive-Negative Balanced loss and Client Balanced Reweighting).

Here is how they break it down using simple analogies:

1. The Three Levels of Messiness

The authors realized that "imbalance" happens in three different ways, like looking at a pile of fruit from a microscope, a window, and a drone:

  • Inter-Case (The Microscope View):
    • The Problem: Imagine a specific disease, like "Pneumonia." For every one patient who has pneumonia, there might be 100 who don't. The AI gets lazy and just guesses "No Pneumonia" for everyone because it's right 99% of the time.
    • The Fix: The AI needs to be forced to pay extra attention to the rare "Yes" cases.
  • Inter-Class (The Window View):
    • The Problem: Now look at the whole fruit basket. Maybe you have 1,000 apples, 100 oranges, but only 5 bananas. The AI becomes an "Apple Expert" but a terrible "Banana Expert" because it never saw enough bananas.
    • The Fix: The AI needs to be told, "Hey, those 5 bananas are super important! Don't ignore them."
  • Inter-Client (The Drone View):
    • The Problem: Imagine Hospital A has 10,000 patients but they are all "Apple" cases. Hospital B has only 100 patients, but they are a perfect mix of Apples, Oranges, and Bananas.
    • The Old Way: The central server usually says, "Hospital A has more data, so we'll listen to them 100 times more."
    • The Result: The final AI becomes an "Apple Expert" and forgets everything else.
    • The Fix: The server should actually listen more to Hospital B, because their small dataset is more balanced and teaches the AI a wider variety of lessons.

2. The Solution: FedBB

The authors built a two-part tool to fix these problems:

Part A: The "Fair Teacher" (PNB Loss)

This is a new way of grading the AI during its local training.

  • How it works: Instead of just counting how many times the AI got a question right, this method acts like a strict teacher who gives extra credit for getting the rare or difficult cases right.
  • The Analogy: If a student gets 100 easy questions right but misses the one hard question, the teacher doesn't just say "Good job." The teacher says, "You missed the rare one! That counts for double points." This forces the AI to stop ignoring the minority cases (the rare diseases or the few bananas).
  • Bonus: This works for both "Multi-class" (pick one category) and "Multi-label" (pick many categories at once, like a patient having both pneumonia and a broken rib).

Part B: The "Smart Mixer" (CBR)

This is a new way for the central server to combine the models from all the hospitals.

  • How it works: Instead of just counting how many patients a hospital has, the server checks how balanced their data is.
  • The Analogy: Imagine mixing smoothies. If you have a giant bucket of just strawberry smoothie (Hospital A) and a small cup of a perfect fruit salad (Hospital B), you shouldn't just dump the whole bucket in. You should give the small cup of fruit salad a louder voice in the final mix because it represents a more diverse flavor profile.
  • The Result: The final global model becomes a "Generalist" that is good at diagnosing everything, not just the most common things.

3. Why This Matters (According to the Paper)

The authors tested this on two types of data:

  1. Medical X-rays: Real chest X-rays from different hospitals (NIH and CheXpert datasets).
  2. Natural Images: Standard computer vision datasets like CIFAR (cats, dogs, cars, etc.).

The Results:

  • Better Performance: FedBB beat all other popular methods (like FedAvg, FedProx, MOON) in accuracy. It was especially good at handling the "messy" data where some diseases or objects were very rare.
  • Efficiency: It didn't require a supercomputer. It used the same amount of computing power as the basic method (FedAvg) but got much better results.
  • Privacy: It only needs to know a little bit of statistics (like "how balanced is your data?") rather than seeing the actual patient files, which keeps privacy safe.

Summary

The paper argues that to build a truly smart AI in a privacy-friendly way, we can't just throw all the data together. We have to:

  1. Teach the local AI to care about the rare cases (using the PNB Loss).
  2. Listen to the local AI that has the most diverse data, even if it's smaller (using CBR).

By doing this, the final "Global Brain" becomes fairer, more accurate, and ready to handle the real world, where data is rarely perfect.

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 →