Access Multiplexer IP Header Routing for Terminal Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for transmitting information from terminal systems to networks via access multiplexers with virtual forwarder systems are complex due to the need for Ethernet bridges and extensive unpacking and detection at higher layers, especially when handling multiple destinations and service providers.
Innovation Solution
Incorporating a sender in the access multiplexer to send a virtual forwarder IP address to the terminal system, which inserts this address into the destination field of the IP header and a destination IP address into the routing field, allowing direct routing without an Ethernet bridge and reducing complexity by eliminating the need for unpacking and detection at higher layers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If an Ethernet bridge and virtual forwarder system are used for routing control, then routing control capability is improved, but device complexity increases
Solution Approach 1:
The patent extracts the Ethernet bridge component from the system and replaces it with IP address-based routing control. The virtual forwarder system is retained but simplified, eliminating the need for complex Ethernet bridging operations while maintaining routing control capabilities through IP header manipulation.
Solution Approach 2:
The patent substitutes the mechanical/Ethernet-based routing control (Ethernet bridge detecting and selecting based on layer-2 addresses) with an IP-based control mechanism. The terminal system directly inserts virtual forwarder IP addresses into IP headers, replacing the need for Ethernet bridge detection and selection operations.
2Adaptability or versatility
If information is unpacked and detected at higher layers for extended routing control, then routing control precision is improved, but device complexity increases
Solution Approach 1:
The patent applies preliminary action by having the terminal system pre-insert the virtual forwarder IP address into the IP header before the packet reaches the access multiplexer. This eliminates the need for the access multiplexer to unpack and detect information at higher layers, as the routing information is already in place.
Solution Approach 2:
The terminal system performs self-service by autonomously inserting the appropriate virtual forwarder IP address into the IP header based on its own routing decisions. This eliminates the need for the access multiplexer to perform complex unpacking and detection operations, reducing processing complexity while maintaining routing control precision.
3Adaptability or versatility
If Ethernet bridge and virtual forwarder system are used for service differentiation, then service classification capability is improved, but device complexity increases
Solution Approach 1:
The patent changes the parameter used for service differentiation from Ethernet layer-2 addresses to IP layer-3 addresses. The terminal system inserts virtual forwarder IP addresses into the IP header, enabling service classification based on IP address parameters rather than Ethernet address parameters, which simplifies the overall system architecture.
Data Source
AI summary
Systems for transmitting information from terminal systems (1) via access multiplexers (3) comprising virtual forwarder systems (5) to networks are made less complex by inserting at the terminal systems (1) virtual forwarder internet protocol addresses (35,64,66) into destination fields of internet protocol headers for heading the information and by inserting destination internet protocol addresses (36,37,38,65,67) into routing fields of the internet protocol headers. Both the terminal systems (1) and the access multiplexers (3) should be made capable of dealing with internet protocol headers of the internet protocol version-4 or the internet protocol version-6 or higher, which comprise a destination field and a routing field. The destination internet protocol addresses (36,37,38,65,67) in the routing fields allow distinguishment between different classes of services and/or applications used by the terminal system (1) simultaneously, without the access multiplexers (3) being obliged to unpack (parts of) the information and to detect (parts of) the information at higher layers.