Intelligent Satellite Data Node Standardized Interface

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current satellite design is inflexible and costly due to complex wiring and custom configurations, making design changes and reconfiguration time-consuming and expensive.

Innovation Solution

An intelligent satellite data node with a data processing unit and storage unit that converts data streams from various subsystems into a standardized format, allowing plug-and-play functionality and eliminating the need for rewiring by acting as an intermediate layer between subsystems and the on-board computer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If custom hardwire techniques are used for interconnecting subsystems, then communication reliability is improved, but device complexity and wiring harness complexity increase dramatically

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidwiring harness complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a backbone structure with standardized interfaces as an intermediary component between subsystems. This backbone structure provides a pre-established communication network that eliminates the need for complex custom wiring between each subsystem pair. Subsystems connect to the backbone through standardized interfaces, and the backbone routes communications between them, thereby reducing wiring complexity while maintaining communication reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The backbone structure serves multiple functions: it provides mechanical support for subsystems, establishes electrical connections through standardized interfaces, and enables data communication between all connected subsystems. This multi-functional approach replaces multiple specialized connection systems with a single universal infrastructure, reducing overall system complexity.

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

2Reliability

If custom design is used for each satellite, then communication performance is optimized, but manufacturing cost and time increase

Engineering Contradiction:
Improvecommunication performanceVSAvoidmanufacturing cost and time
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent divides the satellite system into independent, modular subsystems that can be developed, tested, and manufactured separately. Each subsystem connects to the standardized backbone interface, allowing them to be produced independently and then integrated. This segmentation enables parallel development and manufacturing, reducing overall production time and cost while maintaining optimized communication performance for each subsystem.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The backbone structure with its standardized interfaces is designed and prepared in advance before subsystem integration. This preliminary establishment of the communication infrastructure allows subsystems to be quickly connected and configured without time-consuming custom wiring during final assembly, thereby reducing manufacturing time and cost.

Inventive Principle:
Principle #10Preliminary action

3Ease of manufacture

If standardized interfaces are used for subsystem connections, then ease of manufacture and reconfiguration are improved, but communication precision and customization capability deteriorate

Engineering Contradiction:
Improveease of manufacture and reconfigurationVSAvoidcommunication precision
Core Design Contradiction:
Ease of manufactureVSManufacturing precision

Solution Approach 1:

The patent applies different levels of standardization: the backbone structure uses standardized interfaces for mechanical and electrical connections to ensure ease of manufacture and reconfiguration. However, the communication protocols and data formats at the subsystem level can be customized to maintain communication precision. This local differentiation allows standardized physical interfaces coexist with customized communication requirements.

Inventive Principle:
Principle #3Local quality

4Reliability

If complex wiring harnesses are used to connect all subsystems, then communication coverage is improved, but weight increases

Engineering Contradiction:
Improvecommunication coverageVSAvoidwiring harness weight
Core Design Contradiction:
ReliabilityVSWeight of moving object

Solution Approach 1:

The backbone structure acts as a centralized communication mediator that consolidates multiple communication paths into a single infrastructure. Instead of requiring direct wiring between each subsystem pair (which would create exponential wiring growth), the backbone provides a shared communication network that all subsystems connect to, dramatically reducing the total amount of wiring and associated weight while maintaining full communication coverage.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3293922B1Intelligent data node for satellites
Publication Date: 2019.01.30 SPACE PROD & INNOVATION UG
  • EP3293922B1 patent drawingFigure 1
  • EP3293922B1 patent drawingFigure 2
  • EP3293922B1 patent drawingFigure 3

AI summary

Intelligent satellite data node (20, 24) for use in a satellite, comprising a data processing unit (140) and comprising a data storage unit (146), further comprising at least one space-qualified data interface (76-86) for a data connection (12, 18) to a subsystem (10, 14), especially a payload or avionics, and/or to an on-board computer (6), whereby said data node (20, 24) for each interface comprises a corresponding connector (230, 234, 244, 248, 252, 256, 274, 278, 284, 288, 294), and whereby said data storage unit (146) is configured to store a plurality of data sheets, and whereby said data processing unit (140) is configured, by employing said data sheet, to convert a data stream of said subsystem (10, 14) to a standardized data stream with a standard format (180) which is defined in said data node (20, 24) and to transmit said standardized data stream to said on-board computer (6) via said data interface.