Multi-Homing Data Interface Selection via Route Scopes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multi-homing network devices are vulnerable to security threats and billing complexities due to the inability to uniquely identify data interfaces and the sharing of port spaces, leading to routing issues and inefficient service usage tracking.
Innovation Solution
A method and system that allow applications on multi-homing network devices to specify network policies for data interfaces, enabling selective data interface usage based on quality, cost, and service requirements, while managing port bindings and routing to ensure secure and efficient data transfer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple data interfaces are opened for direct data transfer, then data service capability and network connectivity are improved, but security vulnerability and attack surface increase
Solution Approach 1:
The patent segments the data interface selection process by introducing route scopes that divide interfaces into application-specific groups. Each application is assigned a specific route scope containing only the interfaces it is permitted to use, thereby segmenting the overall interface set and limiting attack surfaces while maintaining service capability.
Solution Approach 2:
The patent introduces route scopes as an intermediary layer between applications and data interfaces. This mediator controls and regulates which applications can access which interfaces, providing security management without preventing legitimate data transfer operations.
2Productivity
If port space is shared between all data interfaces, then resource utilization is improved, but routing precision and interface identification capability deteriorate
Solution Approach 1:
The patent segments the shared port space by introducing route scope bindings. Each application's route scope specifies which data interfaces can use which ports, creating logical segments within the shared port space that enable precise interface identification while maintaining resource sharing.
Solution Approach 2:
The patent applies local quality by allowing different port binding rules for different route scopes. Each application receives customized port access rights based on its specific route scope, enabling precise control over which applications can bind to which ports on which interfaces.
3Adaptability or versatility
If applications can access any data interface, then service flexibility and adaptability are improved, but billing tracking accuracy and service usage monitoring deteriorate
Solution Approach 1:
The patent segments interface access rights by assigning specific route scopes to applications. This segmentation enables billing tracking because each application's usage can be monitored within its designated route scope boundaries, providing accurate attribution while maintaining service flexibility.
Solution Approach 2:
The patent implements feedback mechanisms where the system monitors and tracks which applications use which interfaces within their route scopes. This feedback enables accurate billing and usage monitoring while applications retain flexibility to use permitted interfaces.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method of transmitting and receiving data from a multi-homing network device to a data network is disclosed and includes defining a network policy and transmitting the network policy to a routing module. Further, the method includes receiving a route scope from the routing module. The route scope identifies a subset of data interfaces to the data network that satisfy the network policy wherein the subset of data interfaces are selected from a set of available data interfaces and wherein the subset of data interfaces includes at least one data interface.