Chapter 02

UTM Architecture and Components

Deep Dive into System Design and Technical Infrastructure

NASA UTM Reference Architecture

The NASA UTM reference architecture, developed through years of research and flight testing, provides the foundational framework adopted globally. This architecture is built on several key principles that distinguish it from traditional air traffic management:

Three-Layer Architecture Model

Layer 1: UAS Operations

The operational layer includes actual drones, pilots/operators, and ground control stations. Drones broadcast Remote ID, follow flight plans, and maintain connectivity with their USS. Operators interact with USS interfaces to plan flights, obtain authorizations, and monitor operations.

Layer 2: UTM Services (USS Network)

The service layer consists of USS providers offering flight planning, authorization requests, conformance monitoring, alerts, and coordination. Multiple USS compete while sharing critical safety information through standardized interfaces. This layer represents the core innovation of UTM—commercial service provision of safety-critical airspace management functions.

Layer 3: Government Services (FIMS)

The authoritative layer provides airspace constraints, approves/denies operations, interfaces with traditional ATC, and coordinates between USS. FIMS acts as the single source of truth for regulatory constraints while enabling the competitive USS marketplace below.

弘益人間 Implementation

The federated architecture ensures no single entity controls access to airspace. By requiring USS to share safety data while competing on service quality, UTM creates an equitable system where small operators get the same airspace access as large corporations—truly benefiting all humanity.

Flight Information Management System (FIMS)

FIMS serves as the government-operated authoritative component connecting USS networks to traditional aviation infrastructure. While USS providers handle day-to-day operations, FIMS maintains overall safety through several critical functions:

Core FIMS Capabilities

Function Description Purpose
Constraint Distribution Publishes airspace restrictions, NOTAMs, TFRs, weather Single authoritative source of operational limits
Authorization Gateway Approves/denies operation requests from USS Ensures compliance with regulations and safety standards
USS Discovery Registry of certified USS providers and coverage areas Enables operators to find and USS to coordinate with each other
ATC Interface Bidirectional data exchange with traditional air traffic control Awareness and coordination between manned/unmanned operations
Data Archiving Records all operations for investigation and analysis Safety improvement and incident investigation

FIMS Data Flows

FIMS continuously publishes authoritative datasets that USS must consume and respect:

When a USS submits an operation request, FIMS performs automated compliance checking against these constraints. Simple operations in uncongested airspace receive instant approval; complex operations near airports or in constrained airspace may require additional review or coordination with ATC.

UTM Service Suppliers (USS) - Detailed Architecture

USS Core Services

USS providers implement a comprehensive suite of services supporting the complete operational lifecycle:

1. Strategic Deconfliction

Before flight, USS compares planned operations against accepted operations from all USS (received via USS-USS data exchange). The system identifies potential conflicts—situations where two operations would occupy overlapping 4D volumes (3D space + time). Conflicts must be resolved before authorization, either by adjusting flight times, altitudes, or routes.

2. Flight Planning and Optimization

USS provides tools for operators to plan routes considering airspace constraints, weather, terrain, obstacles, and operator preferences (speed, efficiency, noise). Advanced USS use AI/ML to optimize routes automatically, suggesting alternatives that reduce flight time or avoid congested areas.

3. Authorization Request Processing

USS submits operation requests to FIMS on behalf of operators. The request includes operation details: geographic bounds, altitude range, start/end times, drone capabilities, operator credentials. FIMS responds with approval, denial, or conditional approval requiring modifications.

4. Real-Time Conformance Monitoring

During flight, USS monitors drone positions (from Remote ID or direct telemetry) against authorized flight volumes. Deviations trigger alerts to the operator and potentially to other USS if safety margins are exceeded. USS may implement automated mitigation, such as commanding return-to-home if the drone leaves its authorized area.

5. USS-to-USS Coordination

USS exchange critical safety information including accepted operations, activated operations, and position reports. This federated data sharing enables each USS to maintain airspace awareness without centralized control. The ASTM F3548 standard defines these exchange protocols.

6. Alerts and Notifications

USS informs operators of relevant events: new TFRs affecting their route, weather deterioration, proximity to other operations, equipment anomalies. Multi-channel notifications (app, SMS, email) ensure critical information reaches operators immediately.

USS Service Component Pre-Flight In-Flight Post-Flight
Planning Route optimization, constraint checking Dynamic rerouting Flight analysis, logging
Authorization FIMS submission, approval management Activation notification Closure confirmation
Monitoring Pre-flight equipment checks Position tracking, conformance Deviation analysis
Coordination Deconfliction with other USS Real-time conflict detection Incident reporting

USS Technical Requirements

To maintain safety and interoperability, USS must meet stringent technical requirements:

Data Exchange Standards and APIs

ASTM F3548 - USS Network Standards

The ASTM F3548 standard defines how USS exchange data, enabling the federated architecture. Key aspects include:

Operation Intent Exchange: USS share planned operations using standardized JSON schemas. An operation intent includes:

{
  "operation_id": "uuid",
  "uss_base_url": "https://uss.example.com",
  "state": "Accepted | Activated | Ended",
  "volumes": [
    {
      "volume": {
        "outline_polygon": {
          "vertices": [[lat, lng], ...]
        },
        "altitude_lower": {"value": 50, "reference": "W84", "units": "M"},
        "altitude_upper": {"value": 120, "reference": "W84", "units": "M"}
      },
      "time_start": "2025-01-15T14:00:00Z",
      "time_end": "2025-01-15T14:30:00Z"
    }
  ],
  "uas_state": "Nominal | Contingent | NonConforming"
}

Remote ID Data Formats (ASTM F3411)

Remote ID messages broadcast from drones include:

FIMS API Endpoints

USS interact with FIMS through REST APIs:

Supporting Systems and Technologies

Geospatial Information Systems

UTM relies heavily on GIS technologies to manage complex 3D airspace. Systems process terrain elevation data, obstacle databases, building heights, vegetation, and temporary structures to create accurate operational volumes. Advanced implementations use LiDAR-derived digital elevation models for centimeter-level accuracy.

Weather Integration

Weather significantly impacts small UAS operations. UTM integrates weather data at unprecedented granularity—hyperlocal forecasts for specific flight corridors, wind shear alerts at low altitudes, icing conditions. Machine learning models predict micro-weather phenomena affecting drone operations.

Identity and Access Management

Robust authentication ensures only authorized operators and certified drones access airspace. Systems verify pilot credentials, drone registration, insurance, and operational permissions. Integration with government databases enables automated compliance checking.

Key Takeaways

Review Questions

  1. Explain how the three-layer architecture (Operations, USS, FIMS) separates concerns while maintaining overall system safety.
  2. What specific functions does FIMS perform that cannot be delegated to USS providers, and why must these remain government responsibilities?
  3. Describe the strategic deconfliction process and how it prevents conflicts before flight rather than relying on in-flight collision avoidance.
  4. How do USS-to-USS data exchanges work according to ASTM F3548, and why is this exchange critical for federated operations?
  5. Compare conformance monitoring during flight with pre-flight strategic deconfliction—how do these complementary approaches enhance safety?
  6. Why does the USS model use multiple competing providers rather than a single government-operated system? What benefits and challenges does this create?
  7. How do Remote ID data formats (ASTM F3411) support both ground-based tracking and airborne detect-and-avoid systems?

弘益人間 · Benefit All Humanity

Federated architecture ensures no single entity controls airspace—democratizing access for all.

📐 시뮬레이터 패널 1