Spacecraft Network Management Distributed Architecture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Spacecraft network management systems face unique challenges due to isolation, harsh environmental impacts, and lack of human intervention, requiring high reliability, autonomy, and redundancy, which existing terrestrial network management systems cannot adequately address.

Innovation Solution

A distributed spacecraft network management system with a dual-path communication approach for user and network management data, utilizing entities like attendant, accessor, collector, logic, and watchdog entities, and common elements such as device and management agents, to ensure robustness and autonomy, with redundant components for immediate activation in case of failure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a centralized network management architecture is used, then system simplicity is improved, but reliability and autonomy deteriorate due to single point of failure risk

Engineering Contradiction:
Improvesystem simplicityVSAvoidreliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent divides the network management system into multiple distributed management entities (MEs) that are spatially separated and functionally independent. Each ME can autonomously manage specific network segments, eliminating the single point of failure inherent in centralized architectures. This segmentation allows the system to maintain reliability while managing complexity through modular design.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from a single-dimensional centralized management model to a multi-dimensional distributed architecture where management functions are spread across multiple spatial locations and hierarchical levels. This dimensional expansion enables fault tolerance through geographic and functional distribution while maintaining system coherence through standardized protocols.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If redundant components are added to improve reliability, then system robustness is improved, but device complexity increases

Engineering Contradiction:
ImproverobustnessVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements redundant management entities as functional copies that can assume each other's roles upon failure. These copies maintain identical or near-identical operational capabilities, allowing seamless failover without requiring complex reconfiguration. The redundancy is achieved through standardized interfaces and protocols that enable interchangeable operation of backup components.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent dynamically adjusts operational parameters such as entity activation states, communication routing paths, and resource allocation based on system conditions and failure scenarios. This parameter flexibility allows the system to optimize between redundancy utilization and complexity management, activating redundant components only when necessary while maintaining system robustness.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If human intervention is required for failure recovery, then operational control is improved, but response time and productivity deteriorate

Engineering Contradiction:
Improveoperational controlVSAvoidresponse time
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent enables management entities to autonomously detect failures, diagnose problems, and execute recovery actions without human intervention. Each ME possesses self-diagnostic and self-healing capabilities through automated monitoring, fault detection algorithms, and pre-programmed recovery procedures. This self-service approach maintains operational control through distributed intelligence while dramatically improving response time by eliminating human reaction delays.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent implements continuous feedback loops where management entities monitor system health, detect anomalies, and automatically adjust operations to maintain reliability. Real-time feedback from network components triggers autonomous recovery actions, creating a closed-loop control system that responds immediately to failures without requiring human analysis or decision-making, thus improving both response time and operational control.

Inventive Principle:
Principle #23Feedback

4Productivity

If newer technology components are used, then productivity and power efficiency are improved, but reliability deteriorates due to lack of proven track record in space environment

Engineering Contradiction:
Improvepower efficiencyVSAvoidproven reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent designs management entities with universal interfaces and standardized protocols that can accommodate different hardware platforms and technology generations. This multi-functionality allows the system to integrate both proven space-qualified components and newer high-efficiency components without compromising reliability, as the management layer abstracts away hardware-specific variations and applies consistent operational standards across all components.

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

Data Source

PatentUS11240116B2Spacecraft network management system and method
Publication Date: 2022.02.01 THE BOEING CO
  • US11240116B2 patent drawing
  • US11240116B2 patent drawing
  • US11240116B2 patent drawing

AI summary

A spacecraft network management system includes five functional entities, namely, attendant, accessor, collector, logic, and logic watchdog in a distributed architecture configured with both in-band and out-of-band data paths. Management data is structured so that it can travel over either in-band or out-of-band and be identified as such; user data travels over in-band paths. These five entities are distributed over the units of the design and then a modified set of otherwise standard elements are assigned to each entity depending on the nature of its function. These elements include managers, management agents, device agents, device management information base, and manager management information base that enable the entities to perform their respective functions.