UTM Service Wrappers for Secure Microservice Data Exchange

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing complexity of air traffic management due to the growing presence of unmanned aircrafts requires a structured and standardized system for data management and performance standards to ensure safety, security, and scalability across global airspace, particularly in shared environments with manned aircraft.

Innovation Solution

The implementation of an unmanned traffic management (UTM) system that utilizes service wrappers to standardize data interfaces and enforce end-to-end performance standards, allowing for modular and interchangeable microservices and macroservices, ensuring safety-critical compliance through authentication and cryptographic methods, and providing a flexible platform for dynamic service selection and infrastructure switching.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a structured and standardized system for data management is implemented to ensure safety and security, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improvesafety and securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system is divided into independent microservices that can be developed, deployed, and managed separately. Each microservice handles specific air traffic management functions, allowing the complex system to be broken down into manageable components while maintaining overall reliability through standardized interfaces and protocols.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Service wrappers are introduced as intermediary components that standardize data interfaces between microservices and the UTM platform. These wrappers enforce performance standards and authentication protocols, ensuring safety and security without requiring direct complex interactions between all system components.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If modular and interchangeable microservices are used to provide flexibility and scalability, then adaptability is improved, but device complexity increases

Engineering Contradiction:
Improveflexibility and scalabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Service wrappers provide universal standardized interfaces that work across all microservices in the system. This allows different microservices to be interchangeably deployed while maintaining consistent data management and performance standards, enabling flexibility and scalability without proportionally increasing system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If end-to-end performance standards and authentication methods are enforced to ensure safety-critical compliance, then reliability is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvesafety-critical complianceVSAvoidoperational simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

Service wrappers automatically enforce performance standards and authentication protocols without requiring manual intervention. The system self-regulates compliance through automated verification and enforcement mechanisms, maintaining safety-critical standards while reducing operational burden.

Inventive Principle:
Principle #25Self-service

4Speed

If real-time data processing is implemented for safety-critical functions, then speed is improved, but device complexity increases

Engineering Contradiction:
Improvereal-time responseVSAvoidsystem complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

Real-time processing requirements are distributed across multiple specialized microservices, each handling specific safety-critical functions. This segmentation allows parallel processing of different data streams, achieving real-time response speeds while managing complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11443642B2Secure microservice architecture for unmanned air traffic management
Publication Date: 2022.09.13 A3 BY AIRBUS LLC
  • US11443642B2 patent drawing
  • US11443642B2 patent drawing
  • US11443642B2 patent drawing

AI summary

A platform for unmanned traffic management (UTM) may include a compute system and infrastructure that standardizes and controls aviation data transmitted between service providers, where each service is abstracted from the platform through a service wrapper that enforces the preset data standards. The service wrappers enforce restrictions on the performance and configuration of data from the service provider. The service wrappers are customized to respective services (such as tracking, terrain, or weather), but provide a standard point of interface, security, and trust between the platform and any services directed to provide a similar function. Upon the request of a user or service providers to obtain aviation data, the UTM platform selects a service providing that aviation data, and provides connection data to the user while protecting the security and integrity of the data. Computationally-intensive tasks that require data from supporting services can be bundled or grouped together as a single service with a service wrapper providing a single point of interface. Bundled services can be designed to as to maintain verifiability and/or safety-criticality of the data passed therethrough.