- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2(+1)
Read review
Paper summary
This paper proposes LoGic, a privacy-preserving cloud-edge collaborative LLM reasoning framework. Its core idea is that, rather than preserving surface semantics, privacy-preserving collaboration should prioritize preserving the logical structure that is critical for reasoning. On the edge side, LoGic decomposes each private query into a Logic Skeleton and an Entity Mapping, applies sensitivity-aware differentiated LDP protection to the two components, and optimizes the extractor using a privacy-aware dual-reward GRPO strategy. The cloud-side LLM then generates a structure-consistent analogical example from the protected representation, and the edge-side SLM performs structure-aligned analogical pattern transfer to solve the original private query. Experiments are conducted on MathQA and StrategyQA, with comparisons against multiple privacy-preserving and cloud-edge collaborative reasoning baselines. The results show that LoGic generally achieves stronger performance than the compared privacy-preserving methods, together with several additional analyses of the proposed framework.
Critical strengths
The paper explicitly decomposes each query into a logic skeleton and an entity mapping, and uses the cloud-side LLM to generate a structurally consistent analogical reasoning example. The overall framework is well aligned with the central motivation of preserving reasoning-critical logical structure rather than surface semantics.
The paper includes overall performance comparisons, component ablations, privacy-budget analysis, evaluations with different judge models and cloud LLMs, as well as reasoning-time efficiency analysis, covering the main aspects of the method’s effectiveness and robustness.
Critical weaknesses
The empirical Leakage metric is mainly based on LLM judgments, while the paper does not include explicit reconstruction, attribute-inference, linkage, or similar attack experiments conducted from the cloud side or over the communication channel. As a result, the current evaluation does not sufficiently demonstrate that the preserved logical structure cannot itself be exploited to infer private information.
Although LoGic generally outperforms Edge-Only and the privacy-preserving baselines, it still shows a clear performance gap from Cloud-Only. Moreover, the improvement diminishes as the edge-side model becomes stronger. This raises concerns about the practical usefulness of the method, since the privacy–utility trade-off is not convincingly demonstrated under stronger edge models.
The efficiency analysis compares LoGic only with several privacy-preserving cloud-edge collaborative reasoning methods, without including Cloud-Only, Edge-Only, or a matched non-private cloud-edge variant. Therefore, it is difficult to quantify the additional resource overhead introduced specifically by the privacy-preserving mechanism, including potential communication and end-to-end latency costs in realistic deployment.
The experiments only cover static QA datasets such as MathQA and StrategyQA, without considering tool-use, code execution, data processing, or similar multi-step interactive settings. Such scenarios also involve substantial privacy concerns, so the current evaluation is insufficient to establish the general applicability of the proposed framework.
The proposed Logic-Entity decoupling is closely related to structured anonymization/de-identification, yet the paper does not provide direct empirical comparisons with such methods. Consequently, the specific differences and relative advantages in terms of privacy, utility, and efficiency remain unclear. The paper also lacks analysis of extraction reliability and computational complexity across different query types.
Questions for authors
Could the authors include an attack-oriented privacy evaluation, for example by attempting to reconstruct the original query, infer sensitive entities or attributes, or perform linkage attacks? Could the current key-noun-based Leakage metric underestimate privacy leakage conveyed through the preserved logical structure?
Compared with Cloud-Only, Edge-Only, and an otherwise identical cloud-edge pipeline without the privacy-preserving components, how much additional latency, memory, computation, and communication overhead does LoGic introduce?
Compared with existing anonymization/de-identification methods, what are the direct advantages of Logic-Entity decoupling in terms of utility, privacy, and efficiency? Are there query types for which a reliable logic skeleton cannot be extracted, or for which extraction incurs substantially higher computational cost?
Does LoGic remain effective in multi-step interactive tasks such as tool-use, code execution, and data processing? If the same user interacts with the cloud multiple times, how are the corresponding privacy budgets composed across interactions?
Response to Reviewer qedR [Part 1/2]
We are grateful for your valuable feedback and constructive comments. We kindly clarify that all of your suggested additional experiments and explanations have been completed and addressed. We also expect to submit the complete revised manuscript in PDF format within the next two days. We would greatly appreciate it if you would reconsider the final evaluation of our work!
Rather than merely combining existing techniques, we propose a logic-structure-driven paradigm for privacy-preserving cloud-edge collaborative inference.
The key novelty of our work lies in redefining the form of information on which cloud–edge collaborative inference relies under privacy constraints: preserve logic structure, not surface semantics. This enables the system to protect private entities while retaining the essential information required for inference.
The non-obvious contributions are threefold.
In summary, we co-design information representation, collaborative reasoning, differentiated privacy protection, and model optimization around the unified goal of preserving reasoning-critical logical structures, establishing a paradigm distinct from approaches that primarily rely on surface-semantic preservation.
The workflow of the structure-aligned analogical pattern transfer module is described in Section 4.3.2, illustrated as part of the overall framework in Figure 1, and further exemplified in Appendix E. Nevertheless, we acknowledge that the existing explanations may not be sufficiently detailed or explicit, and will clarify the relevant descriptions in the revised manuscript.
In this module, the edge-side SLM receives the original private query q together with the analogical example (q^,y^) generated by the cloud, where q^ shares the same logical structure as q and y^ is its complete reasoning trajectory. The edge-side model learns the reasoning pattern of (q^,y^) through prompting, and then transfers this reasoning pattern onto the real private entities of the original query q to produce the final response y. Consequently, this module transfers the reasoning pattern embedded in the analogical example, rather than simply reusing its answer. As stated in lines 329–337: "Given the private query q and the analogical example (q^,y^) returned by the cloud, … , Specifically, the edge-side model first aligns the shared logical structure between q and q^, and then follows the reasoning trajectory y^ to transfer its reasoning pattern to the private entity information."