Davies Meyer – home
    Data3 min read

    Federated Learning

    Federated learning is collaborative model training with distributed data. Participating devices or organisations calculate local model updates that are combined into a shared model. This need not involve collecting raw data centrally. The updates can nevertheless disclose information; decentralised training alone guarantees neither privacy nor a better model.

    Federated Learning explained

    In a typical arrangement, participants receive a model, train locally and transmit updates. These are combined and redistributed through further rounds. McMahan and colleagues describe this approach in their original 2017 paper. The reported results apply to its experimental conditions, not to every of faster or cheaper marketing applications.

    Federated learning is different from simply running a model on a device. It concerns collaboration during learning. Whether the finished service operates locally or centrally is a further architectural decision. A shared model also does not automatically recognise an individual customer’s intent. Training objectives, data meaning and deployment context need to align.

    The original paper identifies privacy limitations of updates. Additional methods such as secure aggregation or differential privacy can reduce particular risks, depending on implementation; they are not automatically included. Also check unreliable participants, different data distributions and faulty contributions. Many participating devices guarantee neither representative data nor equally good results for all groups.

    Creative Engineering starts by asking whether collaborative learning can solve a specific task better than a simpler alternative. We take responsibility for the concept and quality. Compare practical model performance and full effort, including communication, local computation, safeguards and operation. Data do not become unrestricted merely because they remain in place during training.

    Examples

    Hypothetical application

    Several sites want to trial a model for recognising faults in their own machine images. They agree on image categories and separate evaluation data. Local updates contribute to a shared model. The team examines recognition quality at each site and additional operating effort before deciding on deployment.

    Key Points

    • Distinguish collaborative training from merely running a model locally.
    • Protect updates and participating systems deliberately.
    • Assess performance and effort in the actual deployment settings.

    Practical application

    First establish why collaborative training is needed. Define participants, objectives, data rules and independent evaluation; compare quality and effort with a simpler alternative.

    Useful measures

    Performance by deployment setting

    Check relevant errors on independent data across sites or groups.

    Protection of collaboration

    Document data flows, assumptions and demonstrated safeguards.

    Training and operating effort

    Include communication, local and central computation, maintenance and quality checks.

    Common mistakes

    • Equating local raw data with complete confidentiality.
    • Looking only at a global performance average.
    • Omitting communication and operation from the cost calculation.

    Sources and context

    Frequently Asked Questions about Federated Learning

    Raw data need not be transferred centrally. Model updates nevertheless contain learned information and may enable inferences. Protecting their transmission requires separate measures.

    Loading related terms…

    All Terms