Traffic Tagging for Android Proxy Loop Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication technologies fail to efficiently differentiate data packets sent by Android applications and local proxies, leading to inefficient acceleration processing and inability to control acceleration for system applications, resulting in affected application efficiency.
Innovation Solution
A method that determines whether a data packet's tag matches a preset reference tag, redirecting and configuring the packet with the reference tag if it does not match, allowing for differentiation and acceleration control of various applications, including system applications, without altering key Linux modules like Netfilter and TCP/IP.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If Iptables redirection rules are configured to direct data packets to local proxy, then data packet routing is improved, but data packets sent by local proxy are incorrectly redirected again causing endless loops
Solution Approach 1:
The patent introduces an intermediary mechanism (tag marking) between the Netfilter redirection and the local proxy processing. By adding a tag to data packets that have been redirected, the system creates a mediator that prevents the proxy's response packets from being redirected again, thus solving the endless loop problem while maintaining the redirection functionality.
2Reliability
If service port filtering is configured to prevent endless loops, then redirection loops are avoided, but acceleration control for different applications including system applications is lost
Solution Approach 1:
The patent applies local quality by differentiating data packets based on their source application characteristics (uid, package name, process name) rather than applying a global filtering rule. This allows the system to mark and control acceleration for specific applications including system applications, while only redirecting the appropriate packets and avoiding endless loops for marked packets.
3Productivity
If full acceleration processing is applied to all redirected packets, then acceleration coverage is maximized, but acceleration control for specific applications on acceleration whitelist cannot be implemented
Solution Approach 1:
The patent implements partial action by selectively applying acceleration only to packets that match the acceleration whitelist criteria. The system marks packets from applications on the whitelist with a specific tag, and only these marked packets receive acceleration processing. This allows control over which applications are accelerated while maintaining the ability to provide full acceleration coverage for the designated applications.
Data Source
Figure 1~2
Figure 3
Figure 4~5
AI summary
The present disclosure provides a method and a device for directing traffic. The method includes: determining whether a tag of a to-be-sent data packet is same as a reference tag configured in a preset matching rule; under situations where a determination result is that tag of the to-be-sent data packet is not the same as the reference tag configured in the preset matching rule, configuring the to-be-sent data packet with the reference tag by redirecting the to-be-sent data packet; sending the to-be-sent data packet configured with the reference tag. The present disclosure solves the issues of the application efficiency of the acceleration products being affected by the fact that the acceleration solutions in related technologies fails to satisfy the acceleration control demands on different applications and that the system applications cannot be accelerated.