Skip to main content
5G Media Streaming (5GMS)

Implementation Detail

In short
  • Release 16: 804 of 1623 cases implemented, 116 differ from the specification, 676 absent, 27 where the specification is inconsistent (TS 26.501 V16.15.0, TS 26.512 V16.12.0, TS 26.511 V16.3.0, TS 26.117 V16.2.0).
  • Release 17: 913 of 2240 cases implemented, 128 differ from the specification, 1171 absent, 28 where the specification is inconsistent (TS 26.501 V17.10.0, TS 26.512 V17.10.0, TS 26.511 V17.2.0, TS 26.117 V17.2.0).
  • Release 18: 528 of 4347 cases implemented, 109 differ from the specification, 3699 absent, 11 where the specification is inconsistent (TS 26.501 V18.9.0, TS 26.512 V18.7.0, TS 26.510 V18.5.0, TS 26.511 V18.2.0, TS 26.117 V18.5.0).
  • Release 19 (latest): 628 of 5370 cases implemented, 123 differ from the specification, 4606 absent, 13 where the specification is inconsistent (TS 26.501 V19.4.0, TS 26.512 V19.3.0, TS 26.510 V19.2.0, TS 26.511 V19.0.0, TS 26.117 V19.2.0).
  • Built against: AF: 3GPP Forge 5G_APIs tag TSG109-Rel17 (identical to TS 26.512 V17.10.0); M3 client: 5G-MAG /3gpp-m3/v1; AS: 5G_APIs at Release 17 (identical to V17.10.0 on 2026-10-01); M3: 5G-MAG /3gpp-m3/v1 from rt-common-shared, at the version the build pins; Client: not determinable from the build (hand-written Release 17 models; Media3 ExoPlayer 1.10.0); App Provider: hand-written /3gpp-m1/v2 client (Release 17); 5G_APIs at Release 17.
  • Source of this page: code read against every statement of the specifications on the project page; statements a component cannot meet by construction marked absent by group; 35 cases held because a document they rest on was not obtained, 2026-10-07: each requirement split into the cases its clause defines.

For what the specifications define, see the Technical Analysis. For how to run the tools, see the Tutorials.

Architecture​

The architecture of each release, with the parts the Reference Tools provide and the status of each reference point.

Release 17
Architecture, with Reference Tools statusBased on TS 26.501 V17.10.0, figure 4.1-2
Release 19
Architecture, with Reference Tools statusBased on TS 26.501 V19.4.0, figure 4.1.1-2

Click a figure to enlarge it.

Implementation status​

Each feature, split into its requirements and each requirement into the cases its clause defines: what works, what does not, and why. Filter by component, profile and release; open a feature, then a requirement.

  • Downlink (5GMSd).
  • Uplink (5GMSu).
  • Downlink (5GMSd) and Uplink (5GMSu).
  • AF (5GMS Application Function): rt-5gms-application-function v1.4.7. Built against: 3GPP Forge 5G_APIs tag TSG109-Rel17 (identical to TS 26.512 V17.10.0); M3 client: 5G-MAG /3gpp-m3/v1.
  • AS (5GMS Application Server): rt-5gms-application-server 1.2.5. Built against: 5G_APIs at Release 17 (identical to V17.10.0 on 2026-10-01); M3: 5G-MAG /3gpp-m3/v1 from rt-common-shared, at the version the build pins.
  • Client (5GMS client (Media Session Handler, Media Stream Handler, common library, 5GMS-Aware Application)): rt-5gms-media-session-handler v1.3.0, rt-5gms-media-stream-handler v1.3.0, rt-5gms-common-android-library v1.3.0, rt-5gms-application v1.3.0. Built against: not determinable from the build (hand-written Release 17 models; Media3 ExoPlayer 1.10.0).
  • App Provider (5GMS Application Provider): rt-5gms-application-provider 1.3.0. Built against: hand-written /3gpp-m1/v2 client (Release 17); 5G_APIs at Release 17.
  • Source: code read against every statement of the specifications on the project page; statements a component cannot meet by construction marked absent by group; 35 cases held because a document they rest on was not obtained, 2026-10-07.
3GPP release
628 of 5370 implemented · 123 differ · 4606 absent · 13 where the specification is inconsistentcases, over 1323 requirements

✓ Implemented≠ Differs from the specification– Absent? Specification inconsistent: its text and its OpenAPI or tables disagreei Noted: observed, not a verdict against a clause

Content hosting190 of 956 implemented · 47 differ · 709 absent · 10 where the specification is inconsistent
Content preparation0 of 159 implemented · 159 absent
Network assistance21 of 307 implemented · 1 differs · 285 absent
Dynamic policies67 of 729 implemented · 10 differ · 650 absent · 2 where the specification is inconsistent
Remote control0 of 2 implemented · 2 absent
Consumption reporting48 of 205 implemented · 11 differ · 146 absent
QoE metrics reporting75 of 376 implemented · 16 differ · 284 absent · 1 where the specification is inconsistent
Edge processing1 of 186 implemented · 185 absent
eMBMS delivery6 of 76 implemented · 2 differ · 68 absent
Data collection, reporting and exposure0 of 493 implemented · 493 absent
Service URL handling0 of 66 implemented · 66 absent
Content publishing4 of 360 implemented · 356 absent
MBS delivery0 of 121 implemented · 121 absent
M3 between AF and AS27 of 121 implemented · 4 differ · 90 absent
Media session handling APIs83 of 421 implemented · 21 differ · 317 absent
Provisioning38 of 216 implemented · 4 differ · 174 absent
Profiles, codecs and formats25 of 139 implemented · 114 absent
General43 of 437 implemented · 7 differ · 387 absent
Full audit for members

This page summarises a requirement-by-requirement audit of the code. The full audit (each requirement with its clause quoted, the code that meets or misses it, and the findings) is available to 5G-MAG members through Developer Tools (the Standards2Deployments repository).

Become a member · Request access