{"id":"44d56698-fa5b-46c1-9912-797ad3be43d6","arxiv_id":"2504.21583","paper_version":1,"verdict":"CONDITIONAL","confidence":"HIGH","novelty_score":4.0,"correctness_risk":"low","formal_verification":"none","parameter_count":0,"one_line_summary":"A survey that organizes low-altitude economy networks into a layered architecture and argues that multi-technology integration is the key enabler.","lead":"This paper surveys low-altitude economy (LAE) networks, proposing a three-layer architecture and reviewing how communication, sensing, computing, navigation, flight control, and airspace management technologies must be integrated. It is a synthesis of existing standards and research, aimed at guiding future work in UAV and eVTOL operations.","discovery_kind":"review","skeptic_critique":{"model":"deepseek-v4-flash","headline":"The Introduction's 500-3000 m airspace definition is contradicted by the paper's own applications and cited airspace-management work (e.g., the 'below 400 feet' layer in ref.","rationale":"The paper is a broad, well-structured survey with real strengths: it organizes a large literature into a coherent layered architecture, connects visions to specific IEEE standards, and includes honest 'Lessons Learned' passages acknowledging that performance under interference and congestion remains unvalidated. The central thesis that deep integration is needed is a reasonable synthesis and is not contradicted by any evidence in the text. I therefore do not see a reason to reject or unverify the paper. However, the 500-3000 m altitude definition, placed prominently in the Introduction, is the softest spot: it is inconsistent with the paper's own material, as shown by the 400-ft layered airspace (Section III-C-2, ref. [192]) and the last-mile delivery and rooftop infrastructure examples (Sections IV-A and II-B-1). This makes the architecture's scope internally contradictory. The reader's CONDITIONAL verdict is appropriate; my concrete test would force the authors to either correct the definition or explicitly limit the survey's scope. The standard-status issue (draft P1954, Table IV citations) is a secondary but real reliability concern that reinforces the need for corrections. Overall, the paper is acceptable as a conditional survey, provided the authors reconcile the airspace definition with the applications and standards they actually discuss.","tokens_in":41531,"tokens_out":8015,"duration_ms":79081,"concrete_test":"Extract the operating altitudes used in the applications of Section IV by inspecting the cited sources: for last-mile logistics, [205],[206],[209] and for layered airspace management, the 'below 400 feet' design in [192]. If even one of these scenarios operates below 500 m, then the Introduction's 500-3000 m definition is contradicted by the paper's own application content; the authors should then either revise the definition to the full low-altitude band (e.g., 0-3000 m) or explicitly exclude very-low-altitude operations and restructure the architecture accordingly.","verdict_should_be":"UNCHANGED","load_bearing_attack":"The central claim that efficient LAE networks require deep integration of eight technology domains is a survey-level thesis, and the paper compiles substantial relevant material. However, the paper's scope is anchored to an unusual airspace definition in the Introduction: 'between 500 and 3000 meters above the ground.' That lower bound is internally inconsistent with the rest of the manuscript. In Section III-C-2, the paper cites layered-management work [192] that divides airspace 'below 400 feet' (about 120 m). In Section IV-A, the warehouse-to-retail and retail-to-residential logistics scenarios explicitly include urban obstacles such as pedestrians, vehicles, and buildings, and the cited sense-and-avoid works [205],[206],[209] target altitudes well below 500 m. Section II-B-1 includes rooftop landing platforms as part of the physical infrastructure, which are at or near ground level. If the operational low-altitude band actually starts at ground level (as most regulations, e.g., FAA Class G below 1200 ft AGL, and China's 'low-altitude economy' discourse suggest), then the architecture's Airborne Terminal and Physical Infrastructure Layer and its airspace management models omit a large, high-density segment of LAE operations. The central thesis may still be plausible, but the survey's scoping error weakens the claim that the presented architecture is the foundation for LAE networks. The draft status of IEEE P1954 is an additional reliability concern, but the airspace definition is the more fundamental scope issue.","agreement_with_reader":"agree"},"referee_report":{"model":"deepseek-v4-flash","summary":"This survey paper proposes a vision and a three-layer architecture for next-generation low-altitude economy (LAE) networks, anchored in a set of recent IEEE standards. It then reviews three clusters of enabling technologies—communication/sensing/computing, positioning/navigation/surveillance, and flight control/airspace management—and maps them onto three application scenarios (logistics, rescue, transportation). The paper closes with six future research directions, including adaptive airspace optimization, security, energy management, quantum-driven coordination, generative governance, and 3D coverage. The paper contains no original derivations or experiments; its contribution is a structured synthesis and a taxonomy of technologies and applications.","tokens_in":41954,"tokens_out":5316,"duration_ms":56253,"significance":"As a survey, the paper is timely and addresses a relevant and rapidly evolving topic. It assembles a broad reference set, proposes a clear architectural framework, and explicitly emphasizes multi-technology integration, which is the right lens for LAE networks. Its strengths include the use of recent standards (IEEE 1939.1, 1937.8, 1937.3), the organization of a large body of work into comparison tables, and the concrete application scenarios with illustrative figures. If the scope is corrected and the citation errors fixed, the survey would be a valuable entry point for researchers and standardization efforts. The contribution is not a quantitative or algorithmic advance, and the survey's value depends on the accuracy of its scoping and references.","major_comments":[{"comment":"The Introduction defines the target airspace as \"between 500 and 3000 meters above the ground.\" This definition is internally inconsistent with the rest of the manuscript. Section III-C-2 cites [192] on layered management of airspace \"below 400 feet\" (about 120 m), which is below the stated lower bound. Section IV-A's short-distance delivery scenario explicitly involves pedestrians, vehicles, and buildings and cites sense-and-avoid references [205], [206], and [209] that are relevant to altitudes well below 500 m. The architecture in Section II-B-1 includes rooftop landing platforms, which are at or near ground level. The paper therefore either excludes a large share of actual LAE operations or misstates its own scope. Please revise the airspace definition (e.g., from ground level to 3000 m with a stated decomposition) and make the Introduction consistent with the architecture and application sections.","section":"Section I; Section III-C-2; Section IV-A"},{"comment":"The AI-based MPC row in Table IV lists references [155]–[157]. These references are about Assisted GNSS: [155] is an \"Assisted GNSS\" chapter, [156] is a 5G-assisted positioning paper for GNSS-challenged environments, and [157] is an Assisted-GNSS positioning algorithm. None of them addresses model predictive control. The correct citations for AI-based MPC appear in the text as [200] and [201]. Please correct the table.","section":"Table IV"},{"comment":"The paper refers to \"the P1954 standard [45]\" and the reference list labels it \"IEEE Std P1954, 2021.\" IEEE P1954 is a draft standards project, not an approved standard, and the designation \"Std P1954\" is not a valid published standard citation. Presenting a draft as a ratified standard is misleading for a survey whose authority rests partly on standards. Please state the draft status explicitly and cite the draft number and date correctly, or remove the claim that it is a standard.","section":"Section II-A-3; reference [45]"}],"minor_comments":[{"comment":"The sentence \"improving the positioning accuracy to 250 meters\" (in the discussion of [153]) is confusing: 250 m is not high-precision positioning, and the phrasing suggests an error in reporting the original result. Please check the source and rephrase.","section":"Section III-B-1"},{"comment":"The proposals for enhancing layered management with cloud-based air traffic management, and for cross-zone coordination with automated protocols and edge computing, are stated without citations. Adding references would strengthen those claims.","section":"Section III-C-2"},{"comment":"There are several typographical and grammatical issues, e.g., \"In addition, this standard immunity to space, territory, or terrain limitations\" should read \"In addition, this standard is immune to space, territory, or terrain limitations.\" A careful language pass is recommended.","section":"Section VI (also throughout)"},{"comment":"The comparison of related surveys in Table I is useful, but the selection criteria for inclusion are not stated. Making the selection criteria explicit would improve reproducibility and help readers judge coverage.","section":"Table I"}],"recommendation":"major_revision","confidential_remarks":"The manuscript is a survey with a plausible central thesis and a substantial reference base. The main risks are scope inconsistency in the airspace definition and citation accuracy in key summary tables. These issues are fixable within the scope of a revision and do not require new experiments. The paper contains a noticeable number of self-citations, but they appear topical and do not by themselves create a circularity problem. If the authors address the airspace definition and the citation errors, the survey could be suitable for publication."},"author_rebuttal":null,"desk_editor":{"model":"deepseek-v4-flash","letter":"Let me give you the short version: this is a competent survey of LAE networks, worth sending to a referee, but it is not ready as-is. The central claim — that efficient LAE networks need deep integration of comms, sensing, computing, positioning, navigation, surveillance, flight control, and airspace management — is defensible, and the paper marshals a lot of recent literature to support it. The three-layer architecture is a reasonable organizing scheme.\n\nWhat it does well: it collects recent IEEE standards and connects them to network requirements; the application walk-throughs for logistics, rescue, and transportation are concrete; the summary tables are handy; and the future-directions section is broad, which is normal for a survey.\n\nThe soft spots are real but not fatal. The introduction defines the operational band as 500–3000 m above ground, but the paper's own material — layered management below 400 feet, rooftop landing platforms, last-mile logistics among pedestrians and vehicles — clearly operates below 500 m. That is a scope contradiction, and it matters because the architecture is supposed to be the foundation for LAE. Either the definition should be corrected to start at ground level, or the paper should explain why the sub-500 m layer is excluded. Second, Table IV lists references [155]–[157] for AI-based MPC, but those are A-GNSS papers; the correct MPC references in the text are [200]–[201]. That kind of error undermines confidence in the other tables. Third, P1954 is still a draft standard and is cited as a published standard; that should be flagged.\n\nI would not call the survey groundbreaking — it is an organizational synthesis, not a new result — but it is a legitimate contribution to a hot area. The citation issues are fixable. After corrections, it could become a standard entry point for researchers entering LAE. As is, I would not cite it for specific technical claims without checking the original sources.\n\nRecommendation: send to peer review with major revision, mainly for the airspace definition and citation accuracy. It deserves referee time; not a desk reject.","headline":"A useful but uneven survey of low-altitude economy networks; the multi-technology-integration thesis holds up, but the 500–3000 m airspace definition and a Table IV citation mix-up need fixing before it can be a reliable reference.","tokens_in":42294,"tokens_out":2541,"would_cite":false,"duration_ms":24573,"reading_group":"maybe","serious_thinker":"yes","would_accept_peer_review":true},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"deepseek-v4-flash","headline":"This survey argues that efficient low-altitude economy networks depend on the deep integration of communication, sensing, computing, positioning, navigation, surveillance, flight control, and airspace management.","keywords":["low-altitude economy","UAV networks","eVTOL","multi-technology integration","airspace management","integrated sensing and communication","generative AI","LEO satellites"],"falsifier":"A field trial where hundreds of UAVs operate in the 500–3000 m band using separately optimized, non-integrated subsystems would falsify the necessity claim if it matched the integrated system's throughput, latency, and safety; more narrowly, showing that the 1939.1-2021 grid-routing method fails to keep links stable beyond a few hundred nodes would falsify the scalability premise.","tokens_in":41392,"feed_emoji":"🚁","tokens_out":6226,"duration_ms":55300,"temperature":0.7,"pith_summary":"This survey claims that efficient low-altitude economy networks—those coordinating hundreds to thousands of drones and eVTOL aircraft—cannot be realized by stacking independent technologies. Instead, communication, sensing, computing, positioning, navigation, surveillance, flight control, and airspace management must be deeply integrated into one system. The paper organizes this argument through a three-layer network architecture and three technology-integration clusters, and grounds it in existing low-altitude airspace standards and application scenarios like logistics, rescue, and air taxi. A sympathetic reader would care because the integration thesis determines where standards, research, and design effort should be concentrated.","feed_headline":"Deep tech fusion is key to low-altitude economy networks","feed_subtitle":"A survey argues that eight technology families must fuse before drone and eVTOL fleets can share the sky safely.","key_machinery":"The load-bearing organizing device is the three-layer LAE network architecture combined with three technology-integration clusters. The architecture layers are (1) airborne terminals and physical infrastructure, (2) intelligent collaboration and digital airspace, and (3) multi-collaboration and service assurance; the integration clusters are communication-sensing-computing, positioning-navigation-surveillance, and flight control-airspace management. Every technology in the survey is mapped to a layer and cluster, and the argument is that only by fusing these do the applications and future directions (generative AI, security, energy relay, quantum coordination, governance, and 3D coverage) become feasible.","core_discovery":"On the paper's own terms, the central discovery is a roadmap: low-altitude economy networks differ from traditional UAV networks in scale, coordination demands, and security exposure, so they require a layered architecture (airborne terminal and physical infrastructure, intelligent collaboration and digital airspace, multi-collaboration and service assurance) plus the synergy of technologies grouped as communication-sensing-computing, positioning-navigation-surveillance, and flight control-airspace management. The paper shows how the standards 1939.1-2021, 1937.8-2024, the P1954 draft, and 1937.3-2024 support massive connectivity, seamless coordination, collaborative autonomy, and reliable operations within that architecture. It then illustrates the integrated stack in logistics, rescue, and transportation, and argues that this synergy—not any single technology—is what improves operational efficiency, optimizes airspace usage, and ensures safety.","pith_inferences":["If integration is the bottleneck, then comparative testbeds that run deliberately separated subsystems against an integrated one would quantify the claimed advantage; the paper itself proposes no such metric.","The 500–3000 m airspace definition is a regulatory choice; the same architecture might generalize to other altitude bands, but the paper does not argue for that generalization.","The emphasis on standards suggests the first practical milestone for LAE networks is interoperability across standards-compliant devices, not a single algorithmic breakthrough.","The architecture could plausibly be extended to treat ground vehicles and pedestrians as passive sensing nodes, since the paper already relies on non-collaborative passive sensing, though it leaves that connection implicit."],"forward_implications":["If the integration thesis is right, isolated optimization of individual links or control loops will hit a ceiling, and system design must co-design communication, sensing, computing, and control from the start.","The standards cited in the paper become the concrete scaffolding for large-scale LAE deployment, so their adoption and extension is a near-term actionable step.","Applications such as last-mile delivery, disaster rescue, and urban air mobility all rely on the same integrated stack, meaning application research should be coupled with network-level integration rather than treated separately.","The future directions the paper lists—adaptive optimization, security and privacy, sustainable energy, quantum-driven coordination, generative governance, and LAE-LEO 3D coverage—are all extensions of the core integration claim."],"supporting_citations":[{"why":"Defines a grid-based low-altitude airspace framework with route planning and communication quality requirements, underpinning the massive-connectivity vision.","marker":"[36]"},{"why":"Specifies the cellular communication terminal as the core module for BVLOS control and real-time data exchange, supporting the seamless-coordination vision.","marker":"[39]"},{"why":"Provides the self-organizing, spectrum-agile communications architecture and protocol that enable AI-driven UAV swarm autonomy.","marker":"[45]"},{"why":"Specifies flight monitoring data content and short-message transmission protocols, grounding the reliable-operations vision in concrete standards.","marker":"[52]"},{"why":"Serves as the baseline low-altitude intelligent transportation survey that the paper contrasts with, lacking the full multi-technology integration focus.","marker":"[19]"},{"why":"Provides the 3D coverage and aircraft detection perspective that the paper extends toward coordination and airspace management.","marker":"[20]"},{"why":"Presents the embodied-AI ISC3 framework, the closest prior integration attempt that the paper expands by adding navigation, surveillance, flight control, and airspace management.","marker":"[25]"},{"why":"Supplies the unified integrated sensing, communication, and computation framework that anchors the communication-sensing-computing integration cluster.","marker":"[134]"}],"fun_headline_variants":["Low-altitude networks require tech fusion, not just drones","LAE roadmap: eight tech families must merge for safe skies","Survey: Fusing comms, sensing, and control powers low-altitude economy","Low-altitude economy: architecture and integrated tech for UAVs and eVTOLs","Sharing the sky: how tech synergy enables low-altitude networks"],"cache_read_input_tokens":3200,"weakest_assumption_plain":"The paper assumes that low-altitude airspace spans 500 to 3000 meters above ground and that the cited standards, including the draft P1954, are valid foundations; if either is wrong, the proposed architecture and challenge analysis would be mis-scoped.","fun_headline_variants_meta":{"raw":{"variants":["Low-altitude networks require tech fusion, not just drones","LAE roadmap: eight tech families must merge for safe skies","Survey: Fusing comms, sensing, and control powers low-altitude economy","Low-altitude economy: architecture and integrated tech for UAVs and eVTOLs","Sharing the sky: how tech synergy enables low-altitude networks"]},"model":"deepseek-v4-flash","effort":"low","cost_usd":0.00127,"raw_usage":{"total_tokens":5223,"prompt_tokens":999,"completion_tokens":4224,"prompt_tokens_details":{"cached_tokens":384},"prompt_cache_hit_tokens":384,"prompt_cache_miss_tokens":615,"completion_tokens_details":{"reasoning_tokens":4129}},"tokens_in":615,"tokens_out":4224,"duration_ms":31289,"temperature":1.0,"reasoning_tokens":4129,"cache_read_input_tokens":384,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-08-16T04:57:43.083134+00:00","model_set":{"reader":"deepseek-v4-flash"},"falsifier":"A field trial where hundreds of UAVs operate in the 500–3000 m band using separately optimized, non-integrated subsystems would falsify the necessity claim if it matched the integrated system's throughput, latency, and safety; more narrowly, showing that the 1939.1-2021 grid-routing method fails to keep links stable beyond a few hundred nodes would falsify the scalability premise.","supporting_citations":[],"review_version":1}