Multi-Connectivity Backend for Home Network Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multi-connectivity technologies do not allow for access to a home network without physical attachment, limiting the ability of user equipment to utilize multiple internet access interfaces simultaneously for enhanced reliability and speed.
Innovation Solution
A system comprising user equipment with multiple access interfaces, a multi-connectivity provider backend, and a home network, where the backend establishes a connection to the home network through a data network, allowing access without physical attachment, and manages traffic by determining existing connections and addressing potential IP address conflicts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If standardized multi-connectivity architectures like ATSSS or Hybrid Access are deployed, then traffic management capability and simultaneous connectivity over multiple accesses are improved, but physical attachment to the access provider network is required, limiting flexibility
Solution Approach 1:
The patent introduces a multi-connectivity provider backend as an intermediary component that mediates between the UE and the home network. This backend establishes connections to multiple access networks (cellular, Wi-Fi, fixed) and provides aggregated access to the home network, eliminating the need for UE to physically attach to each access provider network while maintaining multi-connectivity benefits.
Solution Approach 2:
The patent segments the multi-connectivity functionality into separate components: the UE with multiple access interfaces, the multi-connectivity provider backend that manages connections, and the home network. This segmentation allows the backend to handle the complexity of multiple access network attachments while the UE simply needs to connect to the backend, improving flexibility.
2Reliability
If multiple access interfaces are used simultaneously, then reliability and speed are improved, but IP address conflicts may occur between different accesses
Solution Approach 1:
The multi-connectivity provider backend acts as an intermediary that manages IP address allocation and routing for traffic from multiple access interfaces. It prevents IP conflicts by coordinating address assignment and routing traffic appropriately based on the access type and destination, eliminating harmful IP conflicts while maintaining simultaneous multi-access connectivity.
3Adaptability or versatility
If end-to-end multi-connectivity protocols like MPTCP or MP-QUIC are implemented, then multi-path transmission capability is improved, but broad and fast availability is unrealistic due to implementation complexity
Solution Approach 1:
The patent introduces a multi-connectivity provider backend as an intermediary that implements multi-connectivity functionality at the network level rather than requiring end-to-end protocol implementation in UE. This approach enables multi-path transmission capability through the backend's traffic management capabilities while avoiding the deployment complexity of widespread end-device protocol implementation.
Solution Approach 2:
The patent shifts the multi-connectivity implementation from the application/transport layer (end-to-end protocols) to the network layer through the multi-connectivity provider backend. This dimensional change in implementation approach enables faster deployment by leveraging existing network infrastructure and protocols rather than requiring new end-device capabilities.
Data Source
AI summary
A system includes: a user equipment (UE); at least two Internet access providers; a multi-connectivity provider backend; a home network (HN); and a data network (DN). The UE comprises at least two access interfaces. Multi-connectivity is provided between the UE and the HN. The multi-connectivity provider backend is configured to establish a connection to the HN, and to provide the UE with access to the HN.