Mobile Development 22 min read

Evolution of Taobao's Unified Mobile Network Library (AWCN)

The article traces the evolution of Taobao’s unified mobile network library AWCN, detailing its MobileSDN architecture across north‑bound and south‑bound layers, key techniques such as IP‑list scheduling, adaptive protocol selection, multi‑path request handling and vendor acceleration, the challenges faced, performance gains observed during high‑traffic events, and future plans for finer network sensing and intelligent scheduling.

DaTaobao Tech
DaTaobao Tech
DaTaobao Tech
Evolution of Taobao's Unified Mobile Network Library (AWCN)

This article introduces the evolution of Taobao's APP unified network library, AWCN (Ali Wireless Connection Network), and its MobileSDN architecture that spans from monitoring to acceleration across both north‑bound and south‑bound layers.

It first explains the concept of Software Defined Network (SDN) and how the MobileSDN paradigm aligns with the goal of providing a unified, observable, and high‑performance network stack for mobile applications.

The AWCN architecture is broken down into several layers: network applications (e.g., RPC gateway, push, download, image loading), north‑bound interfaces (unified APIs and hooks), network controller (policy scheduling and optimization), south‑bound interfaces (protocol abstraction), protocol forwarding (HTTP/1.1, HTTP/2, HTTP/3, proprietary protocols), and performance management (NPM for DNS, ping, trace, diagnostics).

Key techniques include:

IP strategy scheduling using server‑side IP lists and client‑side dynamic ranking to reduce DNS latency and improve reliability.

Connection and protocol management with hot‑domain pre‑connect, composite connections for IPv6/IPv4 fallback (Happy Eyeballs), and adaptive protocol selection.

Request management with fine‑grained timeout control, multi‑path competition, and fallback to TCP when HTTP/3 degrades.

Vendor acceleration integration, abstracting native system‑level network enhancements (e.g., bandwidth scheduling, dual‑WiFi aggregation).

The article also discusses challenges such as Wi‑Fi BSSID access restrictions on newer Android/iOS versions, the need for new storage keys, and the migration to newer protocols (standard HTTP/2, HTTP/3) while handling stability issues in OkHttp.

Performance results show measurable improvements in latency percentiles (P90, P99, P999) and reduced timeout rates, especially during high‑traffic events like Double‑11.

Future directions focus on more precise network state sensing, dynamic intelligent scheduling, and consistent weak‑network user experiences.

Relevant code reference:

com.android.okhttp
performanceAndroidnetwork optimizationHTTP/2mobile networkingSDN
DaTaobao Tech
Written by

DaTaobao Tech

Official account of DaTaobao Technology

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.