Wei Yang

Wei Yang

Auto-generated profile, based on publicly available information

Wei Yang

Bytedance, Beijing, China

Research Focus & Metrics

Academic Career Length

2Years (2025-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
27 August 2025
Verified
Conference Paper
Open access
WZWei Zhang
Wei Zhang
TMTong Meng
Tong Meng
XZXianhua Zeng
Xianhua Zeng
WYWei Yang
Wei Yang
CYChangqing Yan
Changqing Yan
ZWZhi Wang
Zhi Wang

12 April 2026
Verified
Conference Paper
Open access
LLLiming Liu
Liming Liu
ZJZhidong Jia
Zhidong Jia
LJLi Jiang
Li Jiang
WZWei Zhang
Wei Zhang
LXLan Xie
Lan Xie
XZXinggong Zhang
Xinggong Zhang
Low-latency live streaming (LLS) has emerged as a popular web application, with many platforms adopting real-time protocols such as WebRTC to minimize end-to-end latency. However, we observe a counter-intuitive phenomenon: even when the actual encoded bitrate does not fully utilize the available bandwidth, stalling events remain frequent. This insufficient bandwidth utilization arises from the intrinsic temporal variations of real-time video encoding, which cause conventional packet-level congestion control algorithms to misestimate available bandwidth. When a high-bitrate frame is suddenly produced, sending at the wrong rate can either trigger packet loss or increase queueing delay, resulting in playback stalls. To address these issues, we present Camel, a novel frame-level congestion control algorithm (CCA) tailored for LLS. Our insight is to use frame-level network feedback to capture the true network capacity, immune to the irregular sending pattern caused by encoding. Camel comprises three key modules: the Bandwidth and Delay Estimator and the Congestion Detector, which jointly determine the average sending rate, and the Bursting Length Controller, which governs the emission pattern to prevent packet loss. We evaluate Camel on both large-scale real-world deployments and controlled simulations. In the real-world platform with 250M users and 2B sessions across 150+ countries, Camel achieves up to a 70.8% increase in 1080P resolution ratio, a 14.4% increase in media bitrate, and up to a 14.1% reduction in stalling ratio. In simulations under undershooting, shallow buffers, and network jitter, Camel outperforms existing congestion control algorithms, with up to 19.8% higher bitrate, 93.0% lower stalling ratio, and 23.9% improvement in bandwidth estimation accuracy.

1 November 2026 in IEEE Transactions on Mobile Computing
Verified
Journal Article
Closed access
BLBowen Li
Bowen Li
JJJingyan Jiang
Jingyan Jiang
RLRongwei Lu
Rongwei Lu
YLYixi Lin
Yixi Lin
WZWei Zhang
Wei Zhang
ZWZhi Wang
Zhi Wang


1 June 2026 in Proceedings of the ACM on Networking
Verified
Journal Article
Open access
HYHebin Yu
Hebin Yu
HWHaiping Wang
Haiping Wang
SSSandesh Dhawaskar Sathyanarayana
Sandesh Dhawaskar Sathyanarayana
HFHang Fu
Hang Fu
WZWei Zhang
Wei Zhang
SSShu Shi
Shu Shi
Multipath transport, which simultaneously utilizes Wi-Fi and cellular interfaces, is a promising approach to meet the stringent latency and reliability demands of real-time communication (RTC) applications such as cloud gaming, conferencing, and live streaming. Motivated by prior work demonstrating Quality of Experience (QoE) gains, we developed and deployed a multipath RTC transport using adaptive duplication. However, our large-scale production deployment did not replicate the improvements observed in testbed or emulationbased evaluations, prompting a deeper investigation. To systematically identify deployment bottlenecks, we introduce a seven-layer funnel model spanning user, device, and network layers. To our knowledge, this is the first large-scale deployment study that exposes real-world limitations of multipath RTC transport. Our five-month analysis across 30+ regions in China and over 40 million sessions reveals that sessions with >80% multipath usage achieve a 37.4% reduction in stall rate and a 20.4% decrease in end-to-end (E2E) latency on average. These results show that interpreting A/B outcomes for multipath requires accounting for deployment and session-level activation conditions.