IP Connection Orchestration Using Host Stack Capability Checks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing 5G cellular routers waste resources and decrease operational efficiency due to unawareness of host device IP status, leading to storage and processing of unsupported IPv4/IPv6 addresses, increased network load, and inefficient IP management.
Innovation Solution
A method and device for IP status checking and connection orchestration that determines the IP stack capability of connected devices using protocols like ARP, releases unsupported addresses, and acquires supported ones, reducing memory, CPU usage, and network load.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the AP device keeps global IPv4/IPv6 addresses obtained from the PDN without checking host device IP status, then the device can potentially support both IPv4 and IPv6 hosts, but memory is wasted storing IP-related data for unusable addresses and CPU usage increases running IP management activities for unsupported addresses
Solution Approach 1:
The AP device performs preliminary action by checking the IP stack capability status of the host device before acquiring and storing IPv4/IPv6 addresses from the PDN. This prevents wasting memory on storing IP-related data for addresses that will not be used, while still maintaining the ability to support both IPv4 and IPv6 hosts when needed.
2Adaptability or versatility
If the AP device keeps global IPv4/IPv6 addresses obtained from the PDN without checking host device IP status, then the device can potentially support both IPv4 and IPv6 hosts, but CPU usage increases running IP management activities for unsupported addresses
Solution Approach 1:
The AP device performs preliminary action by checking the IP stack capability status of the host device before acquiring and storing IPv4/IPv6 addresses from the PDN. This prevents wasting CPU resources on running IP management activities for addresses that will not be used, while still maintaining the ability to support both IPv4 and IPv6 hosts when needed.
3Adaptability or versatility
If the AP device keeps global IPv4/IPv6 addresses obtained from the PDN without checking host device IP status, then the device can potentially support both IPv4 and IPv6 hosts, but network resources are wasted due to overhead of storing and managing unusable addresses
Solution Approach 1:
The AP device performs preliminary action by checking the IP stack capability status of the host device before acquiring and storing IPv4/IPv6 addresses from the PDN. This prevents wasting network resources on overhead of storing and managing unusable addresses, while still maintaining the ability to support both IPv4 and IPv6 hosts when needed.
4Productivity
If the AP device checks host device IP status before acquiring IPv4/IPv6 addresses, then memory, CPU, and network resources are optimized, but additional networking messages are exchanged between AP device, PDN, and host devices
Solution Approach 1:
The AP device uses the existing DHCP and Neighbor Discovery protocols as intermediaries to check the IP stack capability status of the host device. These protocols already facilitate communication between the AP device, PDN, and host devices, so the check is performed as part of the normal connection establishment process without adding significant communication overhead.
5Loss of energy
If the AP device releases unsupported IPv4/IPv6 addresses, then resource waste is minimized, but IP management complexity increases due to dynamic address acquisition and release
Solution Approach 1:
The AP device uses feedback from the IP stack capability status check of the host device to dynamically manage IPv4/IPv6 address acquisition and release. The check results provide feedback that guides whether to acquire or release addresses, optimizing resource efficiency while keeping IP management complexity manageable through automated decision-making based on host device capabilities.
Data Source
AI summary
Embodiments herein disclose a method for Device IP Status Checking and Connection Orchestration (DISCCO) by a first electronic device. The method may include receiving a version(s) of an IP address from a backhaul server. The method may include determining an IP stack capability status of a second electronic device using a network protocol(s), where the IP stack capability status indicates whether the received version(s) of the IP address is supported by the second electronic device and the received version(s) of the IP address is enabled on the second electronic device. The method may include storing the IP stack capability status of the second electronic device into a host status database of the first electronic device. The method may include orchestrating the received version(s) of the IP address with the backhaul server and/or the second electronic device based on the stored IP stack capability status.