Shared Switch Virtualization for Aircraft Data Independence
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communications networks for aircraft are burdensome due to the need for multiple switches to ensure data independence within modules and between modules and user terminals, leading to a complex and resource-intensive architecture.
Innovation Solution
A simplified communications network architecture using a single shared switch with multiple configurations, each associated with a module or user terminal, and integrated configuration tables to manage private and public exchanges, allowing for independent data handling and flexible configuration management without affecting the entire system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple switches are used in cascade for each module to ensure data independence, then data independence and security are maintained, but device complexity and resource requirements increase significantly
Solution Approach 1:
The patent merges multiple dedicated switches into a single shared switch by implementing multiple virtual switches within the same physical device. Each virtual switch handles data for a specific module independently through virtualization, eliminating the need for multiple physical switches while maintaining data independence. The shared switch contains multiple configuration tables (first configuration table for module-private data, second configuration table for user terminal data) that operate independently, achieving both consolidation and isolation.
Solution Approach 2:
The shared switch performs multiple functions that previously required separate dedicated switches. It simultaneously handles private data exchanges within modules, data exchanges between modules and user terminals, and maintains independence for each data stream through virtualization. The switch is configured with multiple configuration tables that enable it to serve multiple modules and user terminals with a single device, making it a universal networking component.
2Device complexity
If a single shared switch is used to simplify architecture, then device complexity is reduced, but ensuring data independence between modules and user terminals becomes more difficult
Solution Approach 1:
The patent segments the shared switch into multiple virtual switches, each responsible for specific modules and user terminals. This segmentation is achieved through multiple configuration tables: the first configuration table segments private module data, the second configuration table segments user terminal data, and additional configuration tables segment specific user terminal exchanges. Each virtual switch operates independently with its own configuration, ensuring data independence while using a single physical device.
Solution Approach 2:
The shared switch acts as an intermediary between modules and user terminals, mediating data exchanges while maintaining independence. The configuration tables serve as intermediaries that route and isolate data streams, ensuring that private module data does not mix with user terminal data. The switch mediates all communications through its multiple configuration tables, providing both connectivity and isolation.
3Reliability
If multiple dedicated switches are used for each module, then data exchange independence is ensured, but ease of configuration and maintenance deteriorates due to system-wide reconfiguration requirements
Solution Approach 1:
The configuration space is segmented into independent virtual switches, each with its own configuration tables. When configuration changes are needed for a specific module or user terminal, only the relevant virtual switch and its configuration tables need to be modified. This segmentation isolates configuration changes to specific modules, preventing system-wide reconfiguration and improving ease of operation while maintaining data exchange independence.
4Adaptability or versatility
If a shared switch with multiple configurations is used, then configuration flexibility and independent updates are improved, but the initial setup and management complexity increases
Solution Approach 1:
The shared switch provides universal configuration management that handles multiple modules and user terminals through a single device. The multiple configuration tables (first configuration table for modules, second configuration table for user terminals, and additional tables for specific exchanges) are managed within one switch, providing configuration flexibility while centralizing management. This universal approach allows independent configuration updates for each module or user terminal without affecting others, and reduces the number of physical devices that need to be managed.
Data Source
AI summary
The invention provides a communications network comprising at least two modules and a common switch connected firstly to the two modules and secondly to various different user terminals, the switch having as many configurations as there are user terminals and modules connected to the switch, each user terminal and each module being associated with a particular dedicated configuration.