We consider the federated submodel learning (FSL) problem and propose an approach where clients are able to update the central model information theoretically privately. Our approach is based on private set union (PSU), which is further based on multi-message symmetric private information retrieval (MM-SPIR). The server has two non-colluding databases which keep the model in a replicated manner. With our scheme, the server does not get to learn anything further than the subset of submodels updated by the clients: the server does not get to know which client updated which submodel(s), or anything about the local client data. In comparison to the state-of-the-art private FSL schemes of Jia-Jafar and Vithana-Ulukus, our scheme does not require noisy storage of the model at the databases; and in comparison to the secure aggregation scheme of Zhao-Sun, our scheme does not require pre-distribution of client-side common randomness, instead, our scheme creates the required client-side common randomness via random SPIR and one-time pads. The protocol starts with a common randomness generation (CRG) phase where the two databases establish common randomness at the client-side using RSPIR and one-time pads (this phase is called FSL-CRG). Next, the clients utilize the established client-side common randomness to have the server determine privately the union of indices of submodels to be updated collectively by the clients (this phase is called FSL-PSU). Then, the two databases broadcast the current versions of the submodels in the set union to clients. The clients update the submodels based on their local training data. Finally, the clients use a variation of FSL-PSU to write the updates back to the databases privately (this phase is called FSL-write). Our proposed private FSL scheme is robust against client drop-outs, client late-arrivals, and database drop-outs.
翻译:我们考虑了Federate 子模型学习(FSL) 问题, 并提出了客户可以在理论上私下更新中央模型信息的方法。 我们的方法是以私人设定的联盟(PSU)为基础, 更进一步基于多消息对称私人信息检索( MM-SPIR ) 。 服务器有两个非循环数据库, 以复制的方式保存模型。 与我们的计划相比, 服务器不会学到任何比客户更新的子模型子模型更进一步的东西: 服务器无法知道哪个客户更新了哪个子模型, 或者任何关于本地客户的数据。 我们的方法基于私人设定的联盟( PSUSU) 。 与目前最先进的私人FSL 计划( Jia- Jafar 和 Vithana- Ulukus ) 计划相比, 我们的计划不需要在数据库中杂乱存储模型; 我们的计划不需要事先分配客户端的普通版本, 相反, 我们的FS-L 计划创建的客户端数据库通过随机 SIR 和一次性平台的客户端的客户端数据更新。 协议从普通客户端开始, 在普通客户端的 RRS 版本中, 在普通客户端的版本中, 在普通客户端数据库中, R- R- R- R- R- serl 更新的版本中, 在普通客户端的版本中, 更新的版本中, 在普通客户端的版本中, 更新的版本中, 更新的版本数据库中, 在普通客户端数据库中, 在普通的版本中, 更新的版本数据库中, 在普通客户端数据库中, 正在更新的版本中, 在普通客户端数据库中, 在普通版本中, 更新的版本中, 更新的版本中, 更新。