Meeting: TSGS4_135_India | Agenda Item: 8.7
8 documents found
[FS_QStream_MED] Work Plan for Evaluation of QUIC-based protocols for on-demand and live video services
This contribution proposes a work plan for the Rel-20 study item FS_QStream_MED (Evaluation of QUIC-based protocols for on-demand and live video services), hosted by the MBS SWG.
The study encompasses six main objectives:
Identify application scenarios and their uplink/downlink delivery characteristics for segmented media delivery services, including: - Low latency video streaming - Live streaming - On-demand video platforms - Short-form video platforms
Identify existing and emerging segmented media streaming technologies, specifically QUIC-based technologies from TR 26.804: - DASH over HTTP/3 - MoQ - MPEG-DASH over WebTransport - MPEG-DASH Part 6 over QUIC
Define an evaluation framework for media delivery protocols in the context of 5G Media Streaming (TS 26.501 and TS 26.512):
Determine existing metrics reflecting QoE from relevant specifications (TS 26.247, TR 26.944, ITU-T P.1203, CTA-2066): - Playback time from live edge - Start-up time - Rebuffering events and duration - Streaming quality - Associated QoS metrics
Document potential impacts on: - Media delivery architecture (TS 26.501) - Delivery protocols (TS 26.512) - Codecs and formats (TS 26.511)
Considering factors such as: - Current CDN architectures - 3GPP core network architecture (TS 23.501) - UE implementation - Encrypted content - Caching efficiency - Scalability - Distributed deployment capability - General-purpose implementation readiness
Design a test framework for collecting selected metrics to evaluate baseline (DASH over HTTP 1.1) against identified technologies.
Evaluate selected technologies by collecting QoE metrics under 3GPP network conditions using mobile network traces. This includes: - Developing network simulation setup - Selecting network traces for relevant application scenarios
Note: Objective 4 is split into three phases: - Phase 1: Develop network simulation setup - Phase 2: Select network scenarios - Phase 3: Run experiments and evaluations
If sufficient evidence of benefits is identified:
Study integration of beneficial emerging technologies into 5G Media streaming and identify gaps in: - Architecture (TS 26.501) - Protocols (TS 26.512) - Codecs and formats (TS 26.511) - Relevant video coding tools (e.g., layered video coding, temporal subsequences)
Identify potential normative work requirements for architecture, protocols, and codecs/formats.
Communicate progress to relevant SDOs (IETF MoQ Working Groups) and solicit collaboration with organizations conducting similar work (e.g., SVTA).
Note: ‡ indicates work related to the test platform (TR 26.934)
Agreement is requested on the work plan detailed above.
[FS_QStream_MED] Draft TR 26.934 v0.0.1 - Test platform for media delivery technologies
This is a Release 20 Technical Report (TR) from SA4 (Services and System Aspects) that defines a test platform for evaluating media delivery technologies. The document is in its initial draft stage (V0.0.1) and contains primarily editor's notes outlining the planned structure and content.
This TR is in its earliest draft stage with all technical clauses containing only editor's notes. The structure has been defined but actual technical content, specifications, and details are yet to be populated. The document establishes the framework for a comprehensive test platform that will enable evaluation of media delivery technologies in 3GPP systems.
[FS_QStream_MED] Draft TR 26.835 v0.0.1 - Evaluation of QUIC-based streaming protocols
This is a draft Release 20 Technical Report (TR 26.835 v0.0.1) from SA4 that aims to evaluate QUIC-based streaming protocols for on-demand and live video services. The document is in early template stage with structural placeholders but minimal technical content filled in.
The TR focuses on evaluating QUIC-based streaming protocols as alternatives or enhancements to traditional HTTP/1.1-based DASH streaming for media delivery applications.
Planned Coverage: - Protocols for media streaming (4.2): Will detail specific QUIC-based protocols being evaluated - Multiple protocol subclauses planned covering: - Introduction to each protocol - Technical design - Features - Targeted applications - Baseline protocol: DASH over HTTP/1.1 will be included as the comparison baseline - Other protocols (4.3): QUIC-based protocols not included in the evaluation (may be removed if empty) - Summary (4.4): Comparative overview of protocols
Planned Coverage: - Considered applications (5.2): Media streaming application scenarios to be evaluated - Each scenario will include: - Description - Requirements - Analysis - Metrics selection (5.3): KPIs and performance metrics relevant to the evaluation - Other considerations (5.4): Additional evaluation parameters (may be removed if empty)
Planned Coverage: - Evaluation testbed setup (6.2): Application of TR 26.934 test framework - Test scenarios (6.3): Specific tests to be executed - Each test scenario will include: - Description - Simulation results - Analysis - Test results analysis (6.4): Cross-test comparative analysis - Evaluation summary (6.4 - duplicate numbering in template): Performance comparison against baseline
Planned Coverage: - Study conclusions - Potential recommendations for 3GPP specifications
Planned Coverage: - Information on integrating examined protocols into current media delivery ecosystem - Independent of test results
The TR will: 1. Survey and document relevant QUIC-based streaming protocols 2. Define application scenarios for on-demand and live video services 3. Establish evaluation metrics appropriate for media streaming 4. Leverage TR 26.934 test framework for performance evaluation 5. Compare QUIC-based protocols against HTTP/1.1-based DASH baseline 6. Provide recommendations for potential standardization or adoption
This is a skeleton document (v0.0.1) with only structural placeholders and editor's notes. No technical content, protocol details, evaluation results, or conclusions have been populated yet. The document establishes the framework for a comprehensive evaluation study to be conducted during Release 20 development.
[FS_QStream_MED] [FS_Q4RTC_MED] Design principles for the QUIC test platform
This is a pseudo-CR contribution from Xiaomi to TR 26.934 v0.0.1 "Test platform for media delivery technologies". The document proposes initial design principles for a test platform that will be used to study QUIC-based protocols for media delivery in both segmented media (FS_QStream_MED) and Real-time Communication (FS_Q4RTC_MED) scenarios.
The contribution proposes formatting and structuring Clause 4 of TR 26.934, establishing the foundational organization for documenting the test platform.
The main technical contribution is the definition of a three-block architecture for the test platform:
The contribution establishes placeholders for:
All technical content sections are marked with Editor's Notes, indicating this is an initial structural proposal with detailed content to be added in future contributions.
[FS_QStream_MED] Proposed template for targeted application and services
This contribution from Xiaomi proposes a standardized template for documenting media streaming application scenarios within the FS_QStream_MED study. The document aims to provide structure and consistency when contributors propose new application scenarios for evaluation.
The document references the relevant objectives from FS_QStream_MED that pertain to application scenarios, specifically:
Short-form video platforms
Objective #2: Identification of QUIC-based streaming technologies (DASH over HTTP/3, MoQ, MPEG-DASH over WebTransport, MPEG-DASH Part 6 over QUIC)
The document notes that each service/application may have different metric requirements, necessitating per-service/application analysis.
The main technical contribution is a structured template with four mandatory sections:
Comprehensive details including: - Freeform text describing the use case - Streaming-specific aspects: - Delivery delay characteristics (Live, On-demand) - Content source (Studio, User-Generated) - Content characteristics (Low Bitrate, 4K) - Justification for assumptions - Underlying technologies overview - QUIC relevance: - How the scenario benefits from specific QUIC features - Which QUIC-based protocol from Clause 4.2 of TR 26.835 applies - Rationale for protocol selection - Note: If protocol not listed in 4.2, contributors should first add it there
References Clause 5.2.1.1 of TR 26.835 v0.0.1
Specific technical requirements including: - Media formats - Bitrate allocation - Latency requirements - Startup delay - Other relevant parameters
References Clause 5.2.1.2 of TR 26.835 v0.0.1
Testing and evaluation details: - Test conditions preparation - Proposed relevant metrics (cross-referenced to Clause 5.3 of TR 26.835 v0.0.1) - Evaluation considerations - Additional testing-related information
References Clause 5.2.1.3 of TR 26.835 v0.0.1
The document proposes incorporating Clause 4 (the template) as a new subclause in the FS_QStream_MED Work Plan, providing a standardized approach for all future application scenario contributions.
This is a procedural contribution establishing a framework for future technical contributions rather than proposing specific technical solutions. It aims to ensure consistency and completeness when application scenarios are proposed for the QUIC-based streaming technologies study.
[FS_QStream_MED] Application Scenarios
This contribution addresses the FS_QStream_MED Rel-20 study item, which evaluates whether current and future media services could benefit from QUIC-based streaming technologies compared to TCP-based streaming (HTTP 1.1 and HTTP/2). The document proposes five application scenarios with their delivery characteristics to be considered in the study.
Description: Traditional segmented on-demand streaming where UX is driven by TTFF, rebuffering avoidance, and steady-state quality. Serves as a baseline to evaluate whether HTTP/3 improves startup robustness, reduces rebuffering under loss, and stabilizes bitrate selection without changing application semantics or CDN caching.
Delivery Characteristics: - Latency target: Not live-edge constrained (focus on startup delay and seek response) - Segment/chunking: Typically 2–6s segments, usually no chunking - Session duration: Long (tens of minutes to hours) - Churn: Low (few items per session, seeking within session) - Cacheability: Very high (content reused across many viewers and time) - Traffic pattern: Downlink-dominant
Description: One-to-many distribution with very high fanout where edge replication and caching efficiency are critical. Downlink includes synchronized consumption of common live timeline, significant join/rejoin activity, and sensitivity to end-to-end latency drift. Central for comparing DASH over HTTP/3 versus other QUIC-based options in terms of join time, live latency distribution, stability under congestion/loss, and operational scalability.
Delivery Characteristics: - Latency target: ~15–45+ seconds (service dependent) - Segment/chunking: Typically 6–10s segments, usually no chunking (or chunking not required) - Session duration: Long (tens of minutes to hours) - Churn: Low (infrequent zaps vs. short-form) - Cacheability: High (segments cache-friendly, many viewers request same objects) - Traffic pattern: Downlink-dominant (uplink mostly control/telemetry)
Description: Live services with tight latency budgets (e.g., interactive sports, live commerce, auctions) where tail latency and timeliness are as important as average latency. Uses very small chunks/parts and constrained playback buffers. Primary service risk is not only rebuffering but also late delivery causing latency drift or missed deadlines. Main stress test for QUIC-based approaches, highlighting where HTTP/3's transport properties may improve QoE and where alternatives like WebTransport or MoQ-style object delivery might reduce overhead and improve timeliness under loss and mobility.
Delivery Characteristics: - Latency target: ~2–8s (sometimes ~1–2s in aggressive "ultra-low" configurations) - Segment/chunking: Often ~1–2s segments plus CMAF chunks/partial segments of ~0.4–1.0s - Session duration: Medium to long (minutes to hours, event-driven) - Churn: Medium (more joins/leaves than linear, less than short-form) - Cacheability: Moderate to high (finer chunking increases request/object rate, may reduce cache hit efficiency) - Traffic pattern: Downlink-dominant (uplink mainly interaction/chat signals)
Description: Characterized by extremely high churn with short sessions and frequent abandonment within seconds. Platform relies heavily on prefetch and fast startup. Downlink traffic is bursty with many small or partial transfers, frequent representation switches, and strong dependence on connection reuse and efficient request scheduling. Dominant QoE driver is TTFF rather than steady-state quality. Relevant to quantify QUIC's potential benefits in setup/handshake amortization, reduced head-of-line effects, improved performance under lossy access networks, and reduced per-request overhead.
Delivery Characteristics: - Latency target: Primarily instant start (TTFF is critical "latency" KPI) - Segment/chunking: Very small initial fetches (tiny first segment/chunk/GOP-aligned unit) followed by progressive fetch; segment durations ~1–2s with emphasis on early playable data - Session duration: Variable (often minutes, composed of many short items) - Churn: Very high (many joins/exits per minute) - Cacheability: Mixed (popular clips cache well, but personalization and huge catalog reduce cache hit ratios) - Traffic pattern: Downlink-dominant (plus uplink for telemetry, recommendation signals, occasional UGC upload)
Description: Couples challenging uplink contribution path with large-scale downlink distribution, reflecting modern "creator live" streaming services. Uplink is often mobile and highly variable with fluctuations in available bitrate, RTT, loss, and NAT rebinding. Downlink requires scalable fanout to heterogeneous receivers with frequent joins/rejoins and sensitivity to stalls and latency drift. End-to-end performance frequently dominated by recovery behavior when uplink path changes. Particularly relevant to assess QUIC features supporting robustness and continuity across path changes and to evaluate system-level KPIs such as recovery time after impairment, join/rejoin success rate, and end-to-end latency distributions under mobility.
Delivery Characteristics: - Latency target: Often sub-second to a few seconds contribution delay (compounds into end-to-end latency) - Segment/chunking: Can be chunked (frame/GOP/fragment level) or message/object oriented; if segmented ingest, segments tend to be small and/or chunked to reduce contribution delay - Session duration: Medium to long (minutes to hours) - Churn: Medium (streams start/stop; less rapid than short-form) - Cacheability: Low in uplink leg (ingest traffic unique per stream), though downstream distribution may be cacheable - Traffic pattern: Uplink-dominant on contribution leg (downlink for monitoring/return video is secondary)
The contribution proposes to document all five application scenarios described in section 2 in the new TR for FS_QStream_MED.
[FS_QStream_MED] Media over QUIC
This contribution addresses the FS_QStream_MED Rel-20 study (SP-251659), which evaluates whether current and future media services could benefit from QUIC-based streaming technologies compared to TCP-based technologies (HTTP 1.1 and HTTP/2). The document provides information on Media-over-QUIC (MoQ) as one of the emerging QUIC-based streaming technologies identified in TR 26.804.
MoQ is an IETF working group effort standardizing a publish/subscribe media delivery system over QUIC and WebTransport-over-HTTP/3, designed for high-scale, low-latency delivery with explicit support for intermediaries (relays, caches, replication points).
As of February 2, 2026, the MoQ WG has four core drafts:
MoQT builds upon: - QUIC or WebTransport as underlying transport - HTTP/3 as application-layer substrate - Publisher-subscriber communication model - Optional relay-based distribution mechanisms
Content is organized hierarchically as Track → Group → Object:
Track: Subscribable unit representing logical timeline for one stream of related content (e.g., video encoding, audio language, captions). Publishers advertise/publish Tracks; subscribers subscribe to Tracks.
Group: Ordered collection of Objects within a Track, serving as join point. Subscribers can start at Group beginning and decode without prior Group information. Groups align with random-access boundaries (e.g., GOP/IDR boundaries for video).
Object: Smallest named/addressable payload unit delivered. Contains bytes plus identifiers (Track + Group + Object IDs) and optional metadata. Objects are what relays forward and potentially cache, and the unit MoQT schedules over QUIC streams/datagrams.
The contribution provides detailed mapping between MoQ and DASH concepts:
MSF is the standardized media packaging and signaling layer on top of MOQT, defining how to package and map streaming media onto MoQT's Track/Group/Object abstractions.
CMSF (CMAF-compliant MSF) extends MSF by defining optional feature specifying syntax and semantics for carrying CMAF-packaged media within MSF framework while retaining MSF's catalog/timeline/switching concepts.
The contribution proposes to include the contents of section 2 in the new TR 26.835.
[FS_QStream_MED] Performance and Metrics Evaluation
This change request proposes a framework for performance and metrics evaluation as part of the FS_QStream_MED study item, which is commencing at SA4 Meeting #135.
The document proposes leveraging the existing metrics collection infrastructure with the following approach: