Multiple Network Acceleration SDK offers two traffic takeover methods: VPN and SOCKS5.
Reuse system VPN service via VPN method to intercept traffic under traffic diversion rules. Generally used for accelerator business (i.e., speeding up other apps).
SOCKS5 proxy mode provides a local traffic diversion port. Customers need to configure SOCKS5 traffic diversion rules for the connections they want to accelerate. It is commonly used to speed up traffic within the APP, such as native acceleration for gaming applications and audio/video applications.
Specify Policy Based on Quintuple
Traffic diversion based on quintuple refers to setting separate policies (acceleration mode) for partial quintuples after traffic takeover (VPN and SOCKS5). For example, in some industry scenarios, video streams use aggregation mode, while signaling adopts multiple-transmission selective-reception mode.
Network Interface Card Verification
Multi-channel acceleration is valid only when multiple network interface cards are available on physical devices. Therefore, you need to determine whether to enter or exit the acceleration process based on network interface card availability. The specific logic is as follows:
1. Support NIC verification during startup testing.
2. Support NIC verification during acceleration.
If the current terminal fails to satisfy the set acceleration conditions, it will return error code -22.
Dynamic Acceleration
The access acceleration capacity is divided into two methods: full-time acceleration and dynamic acceleration.
1. Full-time Acceleration
Business (such as game battles, push/pull stream) starts acceleration upon launch and stops when the business ends.
Best acceleration performance with full-process assurance.
2. Dynamic Acceleration
During business, acceleration is only started when there is a potential risk of lag due to poor network connection.
Suboptimal acceleration performance, guaranteed as needed, with certain cost savings.
Dynamic Origin-Pull (Escape)
Dynamic origin-pull (fallback) is the fallback strategy for acceleration. It refers to the fallback strategy when the accelerated link shows suspicious quality degradation or acceleration fails to achieve expected optimization. The primary reason during actual occurrence is poor physical link quality. Note: Dynamic origin-pull will directly terminate the acceleration channel. If acceleration is initiated using a SOCKS5 proxy, the customer needs to adapt the logic to route traffic to the origin server (no need to worry about VPN proxy).
Pull Up VPN and TCP Direct Access in Advance with Dynamic Traffic Switching (Gaming Compatible)
For accelerator business, if adopting a dynamically pulled mode, compatibility needs consideration. For example: in game A, battle traffic uses UDP protocol. Only need to accelerate UDP traffic. Meanwhile, if TCP connections during battles are proxied, compatibility issues may arise (popup/re-entering room/lagging, etc.). At this point, follow these steps:
1. Complete registration in advance, start acceleration (by establishing a VPN), and configure TCP/UDP passthrough before entering the game or room.
2. During game battles, when the acceleration condition is hit, traffic is dynamically switched. At this point, TCP connections remain unchanged, and UDP traffic enters the acceleration pipeline.
3. The acceleration condition is hit and ended, and traffic switching is dynamically completed. At this point, TCP connections remain unchanged, and UDP traffic returns to the origin server.
Multi-NIC Policy for Mobile Phones (Secondary Wi-Fi/Secondary Cellular)
Currently some mid to high-end Android mobile phones support Wi-Fi dual-band/dual SIM dual active (DSDA). At this point, Multiple Network Acceleration SDK can add the secondary Wi-Fi/secondary cellular network to the multi-NIC policy simultaneously. However, please note that the Android system natively supports only one cellular network card and one Wi-Fi card. The secondary Wi-Fi and extended cellular network interface are extension APIs, and implementations vary by manufacturer. In this background, Multiple Network Acceleration provides a unified multi-NIC custom plugin. Customers need to manually adapt the interface based on the multi-NIC extension API provided by the manufacturer. After adaptation, the Tencent Cloud Jutong SDK will introduce custom network cards for multi-NIC acceleration.
