构建跨项目账户的A2A调度中枢,让企业对话界面稳定调用多种后端服务。
Mind the Boundary: Stabilizing Gemini Enterprise A2A via a Cloud Run Hub Across Projects and Accounts
- 在Cloud Run上搭建A2A枢纽,分四路路由请求:跨项目/账户代理、权限保护服务等。
- 实测四类查询均实现确定性路由,检索路径可准确提取15分钟时限关键信息。
- 通过文本兼容模式与REST工具接口分离结构化输出,避免前端错误,适合企业级部署。
企业对话界面需在跨项目与账户边界下安全、可复现地协调异构后端代理与工具。基于Gemini Enterprise A2A调用,我们在Cloud Run上实现一个A2A Hub调度器,支持四条路径:部署于不同项目的公共A2A代理、跨账户受IAM保护的Cloud Run A2A代理、结合Discovery Engine与Vertex AI Search的检索增强生成路径(直接从Google Cloud Storage获取源文本),以及通过Vertex AI的通用问答路径。实验表明,实际互操作性不仅取决于协议合规,还受Gemini Enterprise UI约束和边界依赖认证影响。真实前端请求以纯文本输入,且常携带空的输出模式列表,若在JSON-RPC响应中混入结构化数据会引发界面错误。为此,我们对JSON-RPC端点强制启用纯文本兼容模式,将结构化输出与调试信号移至独立的REST工具API。在覆盖费用政策、项目管理、通用知识与事件响应截止时间提取的四查询基准测试中,验证了确定性路由与稳定前端响应。检索路径授予存储对象读取权限后,成功实现基于证据的15分钟截止时间提取。所有实验可通过标注a2a-hub-gemini-ui-stable-paper的代码仓库快照复现。
原文摘要 · Abstract (English)
Enterprise conversational UIs increasingly need to orchestrate heterogeneous backend agents and tools across project and account boundaries in a secure and reproducible way. Starting from Gemini Enterprise Agent-to-Agent (A2A) invocation, we implement an A2A Hub orchestrator on Cloud Run that routes queries to four paths: a public A2A agent deployed in a different project, an IAM-protected Cloud Run A2A agent in a different account, a retrieval-augmented generation path combining Discovery Engine and Vertex AI Search with direct retrieval of source text from Google Cloud Storage, and a general question answering path via Vertex AI. We show that practical interoperability is governed not only by protocol compliance but also by Gemini Enterprise UI constraints and boundary-dependent authentication. Real UI requests arrive as text-only inputs and include empty accepted output mode lists, so mixing structured data into JSON-RPC responses can trigger UI errors. To address this, we enforce a text-only compatibility mode on the JSON-RPC endpoint while separating structured outputs and debugging signals into a REST tool API. On a four-query benchmark spanning expense policy, project management assistance, general knowledge, and incident response deadline extraction, we confirm deterministic routing and stable UI responses. For the retrieval path, granting storage object read permissions enables evidence-backed extraction of the fifteen minute deadline. All experiments are reproducible using the repository snapshot tagged a2a-hub-gemini-ui-stable-paper.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。