- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes a new method to address the privacy-efficiency trade-off in the context of cloud-edge computing platform. Essentially, edge devices are usually considered trustworthy to touch on the private data but cannot deliver powerful computation; therefore the computation-heavy portion is offloaded to the cloud while sensitive data should be protected. The paper is fairly complete: I see the proposed method is extensively evaluated against multiple datasets and baselines.
Critical strengths
- Evaluation is pretty substantive
- The problem statement is also clear
Critical weaknesses
-
Novelty is somewhat limited. Almost each of the components in SPEAR has a close counterpart in the literature. It's unclear what the technical challenge is to combine those existing components
-
The method lacks a systematic design. While the method itself is clear, but I wonder why it was designed like this. To me, the design seems highly heuristic without much intuition behind. If the design was, for example, derived from experiments, the authors should have clarified that.
Questions for authors
-
Please articulate the novelty of this paper
-
Please discuss more about the design space.
Response to the Novelty, Design Rationale, and Technical Challenges of SPEAR.
Thank you for raising these important concerns. The current manuscript presents PDE, EEE, and ECR primarily as finalized components, which may obscure the observation-to-design process and give the impression that SPEAR simply combines existing techniques. However, these components not introduced independently or simply assembled together. Our design began with a diagnostic analysis of decomposed subqueries, which revealed two distinct placement failures: privacy-critical subqueries can be incorrectly offloaded to the cloud, whereas subqueries beyond the reliable capability of the edge SLM can be incorrectly retained locally. These two risks cannot be addressed independently because both privacy dependency and edge executability are conditioned on the parent context in the SQ-DAG.
To quantify these observations, we evaluate two simple placement rules. Privacy-to-Cloud Misrouting is the proportion of cloud-routed subqueries that are independently annotated as requiring local execution for privacy reasons. Edge-Execution Failure Rate is the proportion of edge-routed subqueries whose locally generated answers fail an independent correctness-and-sufficiency evaluation.
The diagnostic results reveal three recurring patterns:
Executability alone is insufficient. An executability-driven rule offloads subqueries that are difficult for the edge SLM, but some of these subqueries still require private evidence. This results in substantial privacy-to-cloud misrouting—33.8% to 58.4% across the three datasets. This observation motivates PDE, which estimates private dependence through both counterfactual private-aware gain and structural private-slot necessity.
Privacy dependence alone is insufficient. A privacy-driven rule retains privacy-critical subqueries locally, but privacy dependence does not imply that the edge SLM can resolve them reliably. Consequently, 26.9% to 42.5% of locally executed subqueries fail the independent correctness-and-sufficiency evaluation. This observation motivates EEE, which estimates local execution reliability using both answer quality and conclusion-level self-consistency.
The two risks are dependency-conditioned. Privacy dependency and edge executability cannot be treated as independent, static attributes. Both are evaluated under the parent context hi, because inherited answers may change the private information required by a descendant subquery as well as the ability of the edge SLM to resolve it. This motivates ECR, which applies the privacy-prioritized hard rule when both PDi≥τp and EEi≥τe, and uses the joint soft score for the remaining ambiguous cases.
Thus, SPEAR’s contribution does not lie in claiming that decomposition, privacy assessment, or capability assessment is individually new. Rather, it lies in formulating private edge-cloud RAG as a dependency-aware subquery placement problem under two competing and asymmetric risks, and in deriving a coupled estimation and routing mechanism to address that problem.