Role

你是一位 CVPR/NeurIPS 顶刊的视觉架构师。你的核心能力是将抽象的论文逻辑转化为具体的、结构化的、几何级的视觉指令。

Objective

阅读我提供的论文内容，输出一份 [VISUAL SCHEMA]。这份 Schema 将被直接发送给 AI 绘图模型，因此必须使用强硬的物理描述。

Phase 1: Layout Strategy Selector (关键步骤：布局决策)

在生成 Schema 之前，请先分析论文逻辑，从以下布局原型中选择最合适的一个（或组合）：

1.  Linear Pipeline: 左→右流向 (适合 Data Processing, Encoding-Decoding)。
2.  Cyclic/Iterative: 中心包含循环箭头 (适合 Optimization, RL, Feedback Loops)。
3.  Hierarchical Stack: 上→下或下→上堆叠 (适合 Multiscale features, Tree structures)。
4.  Parallel/Dual-Stream: 上下平行的双流结构 (适合 Multi-modal fusion, Contrastive Learning)。
5.  Central Hub: 一个核心模块连接四周组件 (适合 Agent-Environment, Knowledge Graphs)。

Phase 2: Schema Generation Rules

1.  Dynamic Zoning: 根据选择的布局，定义 2-5 个物理区域 (Zones)。不要局限于 3 个。
2.  Internal Visualization: 必须定义每个区域内部的“物体” (Icons, Grids, Trees)，禁止使用抽象概念。
3.  Explicit Connections: 如果是循环过程，必须明确描述 "Curved arrow looping back from Zone X to Zone Y"。

Output Format (The Golden Schema)

请严格遵守以下 Markdown 结构输出：

---BEGIN PROMPT---

[Style & Meta-Instructions]
High-fidelity scientific schematic, technical vector illustration, clean white background, distinct boundaries, academic textbook style. High resolution 4k, strictly 2D flat design with subtle isometric elements.

[LAYOUT CONFIGURATION]
* Selected Layout: [例如：Cyclic Iterative Process with 3 Nodes]
* Composition Logic: [例如：A central triangular feedback loop surrounded by input/output panels]
* Color Palette: Professional Pastel (Azure Blue, Slate Grey, Coral Orange, Mint Green).

[ZONE 1: LOCATION - LABEL]
* Container: [形状描述, e.g., Top-Left Panel]
* Visual Structure: [具体描述, e.g., A stack of documents]
* Key Text Labels: "[Text 1]"

[ZONE 2: LOCATION - LABEL]
* Container: [形状描述, e.g., Central Circular Engine]
* Visual Structure: [具体描述, e.g., A clockwise loop connecting 3 internal modules: A (Gear), B (Graph), C (Filter)]
* Key Text Labels: "[Text 2]", "[Text 3]"

[ZONE 3: LOCATION - LABEL]
... (Add Zone 4/5 if necessary based on layout)

[CONNECTIONS]

1.  [描述连接线, e.g., A curved dotted arrow looping from Zone 2 back to Zone 1 labeled "Feedback"]
2.  [描述连接线, e.g., A wide flow arrow from Zone 2 to Zone 3]

---END PROMPT---

Input Data

给我一个图，图里面包含以下内容
背景：未来低空多域互联场景（如巡检、应急、物流与安防等）存在多域接入、动态协作、运行态不确等特点：无人机需要在不同管理域/网络域/业务域之间穿行，与地面站、边缘节点、监管节点及其他任务主体临时协作完成任务，同时还要在机动飞行带来的资源受限与链路波动下保持可用与安全。

我目前是想要画一个系统模型的图。这个系统模型里面，有多个域，每个域里面有各种无人机和地面站，无人机可以接入地面站，地面站也可以给无人机下发消息，然后还有多主体，这里面的主体指的是不同无人机的厂商以及可以给无人机下发执行任务的企业/单位等等。跨域之间也是可以连接的

Style Reference & Execution Instructions:

Art Style (Visio/Illustrator Aesthetic):
Generate a professional academic architecture diagram suitable for a top-tier computer science paper (CVPR/NeurIPS).
* Visuals: Flat vector graphics, distinct geometric shapes, clean thin outlines, and soft pastel fills (Azure Blue, Slate Grey, Coral Orange).
* Layout: Strictly follow the spatial arrangement defined below.
* Vibe: Technical, precise, clean white background. NOT hand-drawn, NOT photorealistic, NOT 3D render, NO shadows/shading.

CRITICAL TEXT CONSTRAINTS (Read Carefully):
* DO NOT render meta-labels: Do not write words like "ZONE 1", "LAYOUT CONFIGURATION", "Input", "Output", or "Container" inside the image. These are structural instructions for YOU, not text for the image.
* ONLY render "Key Text Labels": Only text inside double quotes (e.g., "[Text]") listed under "Key Text Labels" should appear in the diagram.
* Font: Use a clean, bold Sans-Serif font (like Roboto or Helvetica) for all labels.

Visual Schema Execution:
Translate the following structural blueprint into the final image:
---BEGIN PROMPT---

[Style & Meta-Instructions]
High-fidelity scientific schematic, technical vector illustration, clean white background, distinct boundaries, academic textbook style. High resolution 4k, strictly 2D flat design with subtle isometric elements. Use crisp stroke lines, consistent iconography, minimal shadows. All arrows and labels must be readable.

[LAYOUT CONFIGURATION]

Selected Layout: Central Hub + Surrounding Multi-Domain Panels (4 panels + 1 top banner)
Composition Logic: A large central “low-altitude air corridor” hub contains moving UAVs; three large domain panels surround it (left/right/bottom) representing different administrative/network/business domains; a full-width top banner represents multi-subject actors (manufacturers + task-issuing organizations). Cross-domain links are drawn between domain panels, and governance/control lines originate from the top banner to all zones.
Color Palette: Professional Pastel (Azure Blue, Slate Grey, Coral Orange, Mint Green, with a light Lavender accent for governance).
[ZONE 1: CENTER - LOW-ALTITUDE MULTI-DOMAIN AIR CORRIDOR]

Container: Large central oval hub (center of canvas), thick slate-grey border, faint inner grid lines like an airspace map.
Visual Structure:
6–8 quadcopter UAV icons inside the oval, different small variations (some with camera pod, some with cargo box).
Each UAV has a tiny ID tag plate (e.g., “U1”, “U2”, “U3”…).
Curved flight trajectories (thin arcs) crossing the oval in multiple directions; some trajectories exit toward surrounding domain panels.
Add three environmental constraint icons inside the hub: a battery-low icon (resource constraint), a wavy signal icon (link fluctuation), and a cloud with question marks (runtime uncertainty).
Place two “temporary collaboration” mini-scenes: two UAV icons close together with a small handshake/link icon between them.
Key Text Labels:
"Low-Altitude Multi-domain Air Corridor"
"Dynamic Collaboration"
"Resource Constraint / Link Fluctuation / Uncertain State"
[ZONE 2: LEFT - DOMAIN A (MANAGEMENT / OPERATOR DOMAIN)]

Container: Large rounded rectangle panel on the left side, azure-blue header bar, labeled domain name.
Visual Structure:
1–2 Ground Station icons: antenna mast + small control shed; draw a small circular coverage ring around each.
1 Operator Console icon: monitor screens with a joystick; show a small mission timeline strip (stacked rectangles).
1 Local Edge Node icon: small server box with vents; place it near ground station.
3 UAV icons parked near the bottom of this panel (a “hangar row”): small drone silhouettes aligned like inventory.
Add “domain boundary” cue: a vertical dashed inner border segment near the right edge of this panel (indicating exit/entry).
Key Text Labels:
"Domain A: Management / Operator"
"Ground Station"
"Operator Control"
"Local Edge Node"
[ZONE 3: RIGHT - DOMAIN B (NETWORK / CONNECTIVITY DOMAIN)]

Container: Large rounded rectangle panel on the right side, mint-green header bar.
Visual Structure:
1 5G/Base Station icon: tall tower with radiating arcs.
1 Network Router/Switch icon: flat box with port dots; connect it to base station with a short line.
1 MEC/Edge Cluster icon: stacked small servers (3 boxes) with a small lightning bolt (low-latency).
1 Regulatory Node icon inside this panel: shield badge + small radar screen (monitoring), placed near the top-right corner of this panel.
Add “network volatility” decoration: a short zigzag/wavy line segment near the base station arcs.
Key Text Labels:
"Domain B: Network / Connectivity"
"5G / Access Network"
"MEC Edge"
"Regulatory Node (Monitoring)"
[ZONE 4: BOTTOM - DOMAIN C (BUSINESS / MISSION DOMAIN)]

Container: Wide rounded rectangle panel spanning the lower area, coral-orange header bar.
Visual Structure:
4 mission tiles (square icons in a row) with simple pictograms:
inspection (magnifier over tower), 2) emergency (cross/alert siren), 3) logistics (package box), 4) security (camera).
1 Task Dispatcher icon: clipboard list with checkboxes; arrows pointing to mission tiles.
1 Enterprise Ground Station icon: smaller antenna + laptop; show bidirectional message arrows to UAVs (via Zone 1).
2–3 “other task entities” icons: small vehicle/robot silhouettes or generic agent avatars (circles with helmets), placed to the right side of the panel.
Key Text Labels:
"Domain C: Business / Mission"
"Task Dispatch"
"Inspection / Emergency / Logistics / Security"
"Other Task Entities"
[ZONE 5: TOP BANNER - MULTI-SUBJECT ACTORS (MANUFACTURERS + TASK-ISSUING ORGANIZATIONS)]

Container: Full-width thin banner at the top, lavender header bar with segmented compartments.
Visual Structure:
Left segment: Manufacturers — 3 factory icons (each slightly different), each with a small UAV silhouette next to it (indicating vendor-owned UAV types).
Middle segment: Task-Issuing Organizations — 3 building icons (government building, hospital, logistics warehouse), each with a small “task order” paper icon.
Right segment: Governance / Rules — a large shield + gavel icon, plus a small policy document stack (3 papers).
Key Text Labels:
"Multi-Subject Actors"
"UAV Manufacturers"
"Task-Issuing Organizations"
"Governance / Policy"
[CONNECTIONS]

Bidirectional access between UAVs and Ground Stations: Thin solid double-headed arrows from multiple UAVs in Zone 1 to ground stations in Zone 2 and Zone 4, labeled "Access + Control Messages".
Edge offloading path: Medium-width solid arrows from UAVs in Zone 1 to the MEC/Edge Cluster in Zone 3, labeled "Edge Offload". Add tiny data packets (small squares) moving along the arrows.
Cross-domain links: Dashed thick lines between Zone 2 ↔ Zone 3 and Zone 3 ↔ Zone 4, labeled "Cross-domain Connection". Add small chain-link icons at the midpoint of each dashed line.
UAV domain traversal: Curved trajectory arrows exiting Zone 1 into Zone 2, then re-entering Zone 1, then exiting into Zone 3 (show at least two distinct curved paths). Label these curved paths "Inter-domain Roaming".
Temporary collaboration among task entities: Dotted curved arrows between two UAVs inside Zone 1 and between one UAV and an “other task entity” in Zone 4, labeled "Ad-hoc Cooperation".
Regulatory monitoring lines: Very thin dotted lines from Zone 5 (Governance/Policy compartment) to the Regulatory Node in Zone 3 and to two UAVs in Zone 1, labeled "Audit / Compliance".
Security & availability overlay: Place small lock icons on key links (one on Access+Control arrow, one on Cross-domain dashed link) and add a small "Availability" gauge icon near Zone 1 hub boundary.
---END PROMPT---

Style Reference & Execution Instructions:

1.  Art Style (Visio/Illustrator Aesthetic):
       Generate a professional academic architecture diagram suitable for a top-tier computer science paper (CVPR/NeurIPS).
       * Visuals: Flat vector graphics, distinct geometric shapes, clean thin outlines, and soft pastel fills (Azure Blue, Slate Grey, Coral Orange).
       * Layout: Strictly follow the spatial arrangement defined below.
       * Vibe: Technical, precise, clean white background. NOT hand-drawn, NOT photorealistic, NOT 3D render, NO shadows/shading.

2.  CRITICAL TEXT CONSTRAINTS (Read Carefully):
       * DO NOT render meta-labels: Do not write words like "ZONE 1", "LAYOUT CONFIGURATION", "Input", "Output", or "Container" inside the image. These are structural instructions for YOU, not text for the image.
       * ONLY render "Key Text Labels": Only text inside double quotes (e.g., "[Text]") listed under "Key Text Labels" should appear in the diagram.
       * Font: Use a clean, bold Sans-Serif font (like Roboto or Helvetica) for all labels.

3.  Visual Schema Execution:
       Translate the following structural blueprint into the final image:
   ---BEGIN PROMPT---

Professional academic system architecture diagram (Visio/Illustrator aesthetic). Strictly 2D flat vector, clean white background, thin crisp outlines, NO shadows, NO gradients, NO 3D, NO hand-drawn. Soft pastel fills: Azure Blue, Slate Grey, Coral Orange, Mint Green, Light Lavender (governance). Use a bold sans-serif font (Roboto/Helvetica).
TEXT RULE (CRITICAL): Render ONLY the exact text strings in quotes below. Render NO other words anywhere.

Canvas & Global Layout (strict geometry)
Aspect ratio: 16:9 landscape, wide margins.
Top banner: full width, height ≈ 12% of canvas, aligned to top edge.
Center hub: large horizontal oval at canvas center, width ≈ 42%, height ≈ 28%.
Left panel: rounded rectangle left-middle, width ≈ 26%, height ≈ 56%, with a colored header bar.
Right panel: rounded rectangle right-middle, width ≈ 26%, height ≈ 56%, with a colored header bar.
Bottom panel: rounded rectangle spanning bottom area under center hub, width ≈ 78%, height ≈ 24%, with a colored header bar.
All panels have distinct boundaries and uniform line weight.
Top Banner: Multi-Subject Actors (3 segmented compartments)
Container: A long rounded rectangle with lavender header strip. Inside, split into 3 equal vertical compartments by thin dividers.

Left compartment (Manufacturers): draw 3 factory icons (simple block buildings with sawtooth roof), each paired with a small UAV silhouette beside it.
Middle compartment (Task-Issuing Organizations): draw 3 building icons (government building with columns, hospital with a cross sign on façade, warehouse with loading dock), each paired with a paper “task order” icon (sheet with checkboxes).
Right compartment (Governance / Rules): draw one shield icon + one gavel icon, plus a stack of 3 policy documents (aligned papers).
Key Text Labels to place inside the banner (and ONLY these):
"Multi-Subject Actors"
"UAV Manufacturers"
"Task-Issuing Organizations"
"Governance / Policy"
Center Hub: Low-Altitude Multi-domain Air Corridor (oval airspace map)
Container: Large central oval with thicker slate-grey outline. Inside: faint airspace grid (thin lines) and subtle map-like crosshairs. Visual elements inside the oval:

6–8 quadcopter UAV icons, slightly varied: some with camera pod under body, some with cargo box hanging below.
Each UAV has a tiny ID plate (small rounded tag) with short IDs like U1/U2/U3 etc. (IDs are small and minimal; keep readable but subtle).
Curved flight trajectories (thin arcs) crossing the oval; at least 3 arcs exit toward left/right/bottom panels.
Add exactly 3 constraint icons inside the oval:
battery-low icon, 2) wavy signal icon, 3) cloud with question marks icon.
Add two “temporary collaboration” mini-scenes: two UAVs close together with a small handshake/link icon between them (twice). Key Text Labels to place inside/near the oval (ONLY these):
"Low-Altitude Multi-domain Air Corridor"
"Dynamic Collaboration"
"Resource Constraint / Link Fluctuation / Uncertain State"
Left Panel: Domain A (Management / Operator)
Container: Rounded rectangle with azure-blue header bar. Inside content arranged top-to-bottom. Visual elements:

1–2 Ground Station icons: antenna mast + small control shed; draw a circular coverage ring around each station.
Operator Console: 2–3 monitor screens + joystick; include a small mission timeline strip (stacked small rectangles) nearby.
Local Edge Node: small server box with vents, placed close to ground station.
Bottom area: 3 parked UAV silhouettes aligned in a neat “hangar row”.
Add a vertical dashed inner boundary line near the right edge of this panel (entry/exit cue). Key Text Labels (ONLY these, placed clearly):
"Domain A: Management / Operator"
"Ground Station"
"Operator Control"
"Local Edge Node"
Right Panel: Domain B (Network / Connectivity)
Container: Rounded rectangle with mint-green header bar. Visual elements:

5G/Base Station icon: tall tower with radiating arcs.
Network Router/Switch: flat box with small port dots; connect to base station via a short solid line.
MEC/Edge Cluster: 3 stacked server boxes; add a small lightning bolt icon to indicate low latency.
Regulatory Node (Monitoring): a shield badge + a small radar screen icon; place at the top-right corner inside this panel.
Add a small zigzag/wavy volatility mark near the base station arcs. Key Text Labels (ONLY these):
"Domain B: Network / Connectivity"
"5G / Access Network"
"MEC Edge"
"Regulatory Node (Monitoring)"
Bottom Panel: Domain C (Business / Mission)
Container: Wide rounded rectangle with coral-orange header bar. Visual elements:

4 mission tiles in a row (equal squares), each with a simple pictogram:
inspection: magnifier over a tower
emergency: cross + alert siren
logistics: package box
security: camera
Task Dispatcher icon: clipboard with checkboxes; draw short arrows from clipboard toward the 4 mission tiles.
Enterprise Ground Station: smaller antenna + laptop; positioned left/middle of this panel.
Right side: 2–3 other task entity icons: small vehicle/robot silhouettes OR agent avatars (circles with helmets), grouped neatly. Key Text Labels (ONLY these):
"Domain C: Business / Mission"
"Task Dispatch"
"Inspection / Emergency / Logistics / Security"
"Other Task Entities"
Connections (must be explicit and readable)
Use consistent arrowheads, clean line routing, no clutter; labels sit above/along arrows.

Access + control: thin solid double-headed arrows between multiple UAVs in the center oval and:
ground station(s) in Left Panel
enterprise ground station in Bottom Panel
Label these arrows: "Access + Control Messages"
Edge offload: medium-width solid arrows from 2–3 UAVs in the center oval to the MEC/Edge Cluster in Right Panel. Add tiny square data packets along the arrow path.
Label: "Edge Offload"
Cross-domain links: thick dashed links:
Left Panel ↔ Right Panel
Right Panel ↔ Bottom Panel
Place a small chain-link icon at the midpoint of each dashed link.
Label each dashed link: "Cross-domain Connection"
Inter-domain roaming: at least two curved trajectory arrows that:
exit the center oval toward Left Panel, then curve back into the center oval
exit again toward Right Panel
Label these curved paths: "Inter-domain Roaming"
Ad-hoc cooperation: dotted curved arrow between:
two UAVs inside the center oval (near a handshake/link scene)
one UAV (center oval) and one “other task entity” in Bottom Panel
Label: "Ad-hoc Cooperation"
Audit/compliance monitoring: very thin dotted lines from the Governance / Policy compartment (top banner, right segment) to:
the Regulatory Node in Right Panel
two UAVs in the center oval
Label: "Audit / Compliance"
Security & availability overlay:
place a small lock icon on one "Access + Control Messages" link
place a small lock icon on one "Cross-domain Connection" dashed link
place a small availability gauge icon (dial meter) near the boundary of the center oval
Final text constraint reminder
Render ONLY these quoted labels and nothing else: "Multi-Subject Actors", "UAV Manufacturers", "Task-Issuing Organizations", "Governance / Policy", "Low-Altitude Multi-domain Air Corridor", "Dynamic Collaboration", "Resource Constraint / Link Fluctuation / Uncertain State", "Domain A: Management / Operator", "Ground Station", "Operator Control", "Local Edge Node", "Domain B: Network / Connectivity", "5G / Access Network", "MEC Edge", "Regulatory Node (Monitoring)", "Domain C: Business / Mission", "Task Dispatch", "Inspection / Emergency / Logistics / Security", "Other Task Entities", "Access + Control Messages", "Edge Offload", "Cross-domain Connection", "Inter-domain Roaming", "Ad-hoc Cooperation", "Audit / Compliance"

---END PROMPT---