TS 26.501 defines a set of high-level features for supporting enhanced media streaming in the 5G System. Each applies to downlink, uplink or both.
- 13 features: eight from Release 16, three added in Release 17, two in Release 18, none in Release 19.
- Directions: content hosting, consumption reporting, QoE metrics reporting and delivery via eMBMS and MBS are downlink; content publishing and remote control are uplink; the others apply to both.
- APIs: up to Release 17, TS 26.512 specifies each API with its own OpenAPI file. From Release 18 they are TS 26.510 services that TS 26.512 refers to. Each feature shows both, folded.
- Added in Release 19 in the API tables: in-band CMCD reporting at M4d, content redistribution at M10, and metrics reporting at M3d.
The features
| Feature | Downlink | Uplink | Added in | What it does | Procedures (TS 26.501 V19.4.0 clause) |
|---|---|---|---|---|---|
| Content hosting | ✓ | Release 16 | A service equivalent to a Content Delivery Network (CDN), inside or outside the trusted data network | 5.4 | |
| Content publishing | ✓ | Release 16 | Media from the device is published to the network, which may cache it and prepare it according to templates | 6.2.3 | |
| Content preparation | ✓ | ✓ | Release 16 | Network-side processing from provisioned templates: encoding, transcoding, packaging, encryption, DRM | Not defined |
| Network assistance | ✓ | ✓ | Release 16 | The device asks about, or changes, the network Quality of Service for an ongoing session | 5.9 (d); 6.1, 6.5, 6.7 (u) |
| Dynamic policies | ✓ | ✓ | Release 16 | The device changes how the network handles the traffic of an ongoing session | 5.8, 5.7.6 (d); 6.9 (u) |
| Remote control | ✓ | Release 16 | Not further defined in this release | 6.6 | |
| Consumption reporting | ✓ | Release 16 | Media consumption is logged and exposed for analysis | 5.6 | |
| QoE metrics reporting | ✓ | Release 16 | Quality of Experience (QoE) of sessions is logged and exposed for analysis | 5.5 | |
| Edge processing | ✓ | ✓ | Release 17 | The device uses edge computing in the 5GMS System | 8 |
| eMBMS delivery | ✓ | Release 17 | Downlink content is delivered through eMBMS User Service sessions | 5.10 | |
| Data collection, reporting and exposure | ✓ | ✓ | Release 17 | Session data is logged and exposed to subscribers as events | 5.11 (d); 6.8 (u) |
| Service URL handling | ✓ | ✓ | Release 18 | A 3GPP Service URL, shared in an app, web page or message, launches the service on the device | 9, 5.10.7 (d); 9 (u) |
| MBS delivery | ✓ | Release 18 | Downlink content is delivered through MBS User Service sessions | 5.12 |
(d) is downlink and (u) is uplink. For network assistance in uplink, TS 26.501 table 4.0.1-1 lists clauses 6.5 and 6.7, while clause 4.0.5 lists 6.1, 6.5 and 6.7; the table above follows the clause text.
Consumption and QoE metrics reporting apply to downlink only in the current release. Release 16 (TS 26.501 V16.15.0) defines eight features. Release 17 adds edge processing, eMBMS delivery, and data collection, reporting and exposure. Release 18 adds Service URL handling and MBS delivery. Release 19 adds none to this list.
Feature by feature
For each feature: what it does, where TS 26.501 defines it, and the reference points, APIs and OpenAPI files that implement it. The APIs are in two tables, because Release 18 moved them:
- Up to Release 17: TS 26.512 specifies each API itself, with its own OpenAPI file (
TS26512_M1_…,TS26512_M5_…). The rows come from TS 26.512 V17.10.0 tables 4.2-1 (downlink) and 5.2-1 (uplink). - From Release 18: the provisioning and media session handling APIs are specified in TS 26.510, and TS 26.512 refers to them. The rows come from TS 26.512 V19.3.0 tables 4.2-1 and 5.2-1; the TS 26.510 clause is the one TS 26.512 points to, with its procedure clause in brackets. TS 26.510 clauses 8, 9 and 11 are numbered the same in V18.5.0 and V19.2.0. "Added in Release 19" marks a row that TS 26.512 V18.7.0 does not list.
The OpenAPI file is the one whose title matches the API, in that version's archive. From Release 18, TS 26.512 also ships 5GMS wrapper files (TS26512_Maf_Provisioning.yaml, TS26512_Maf_SessionHandling.yaml) and states that where any discrepancy exists, the version on 3GPP Forge is definitive.
Content hosting
Downlink · added in Release 16 · defined in TS 26.501 clause 4.0.2 · procedures in clause 5.4
Provides a service equivalent to a Content Delivery Network (CDN), inside or outside the trusted data network. Content is ingested pull-based (retrieved from a media origin at the Application Provider) or push-based (published by the Application Provider), may be cached across one or more service locations, may be manipulated according to Content Preparation Templates, and is then retrieved by the 5GMSd Client. A provisioned Server Certificate may secure the content served.
The 5GMSd Client may also be configured to report client data in band with media requests (TS 26.501 clause 5.13).
Up to Release 17 · TS 26.512 V17.10.0, which specifies each API itself
| Reference point | API or protocol | TS 26.512 | OpenAPI file |
|---|---|---|---|
| M1d | Content Protocols Discovery API | cl. 7.5 | TS26512_M1_ContentProtocolsDiscovery.yaml |
| M1d | Provisioning Sessions API | cl. 7.2 | TS26512_M1_ProvisioningSessions.yaml |
| M1d | Server Certificates Provisioning API | cl. 7.3 | TS26512_M1_ServerCertificatesProvisioning.yaml |
| M1d | Content Preparation Templates Provisioning API | cl. 7.4 | TS26512_M1_ContentPreparationTemplatesProvisioning.yaml |
| M1d | Content Hosting Provisioning API | cl. 7.6 | TS26512_M1_ContentHostingProvisioning.yaml |
| M2d | HTTP pull-based content ingest protocol | cl. 8.2 | — |
| M2d | DASH-IF push-based content ingest protocol | cl. 8.3 | — |
| M4d | DASH or 3GP | cl. 10 | — |
| M5d | Service Access Information API | cl. 11.2 | TS26512_M5_ServiceAccessInformation.yaml |
From Release 18 · TS 26.512 V19.3.0, which refers to TS 26.510 V19.2.0
| Reference point | API or protocol | TS 26.512 | TS 26.510 API (procedure) | OpenAPI file |
|---|---|---|---|---|
| M1d | Content Protocols Discovery API (listed in TS 26.512 as its own entry, content protocols discovery) | cl. 7.5 | cl. 8.3 (5.2.3) | TS26510_Maf_Provisioning_ContentProtocols.yaml |
| M1d | Provisioning Sessions API | cl. 7.2 | cl. 8.2 (5.2.2) | TS26510_Maf_Provisioning_ProvisioningSessions.yaml |
| M1d | Server Certificates Provisioning API | cl. 7.3 | cl. 8.4 (5.2.4) | TS26510_Maf_Provisioning_ServerCertificates.yaml |
| M1d | Content Preparation Templates Provisioning API | cl. 7.4 | cl. 8.5 (5.2.5) | TS26510_Maf_Provisioning_ContentPreparationTemplates.yaml |
| M1d | Content Hosting Provisioning API | cl. 7.6 | cl. 8.8 (5.2.8) | TS26510_Maf_Provisioning_ContentHosting.yaml |
| M2d | HTTP pull-based content ingest protocol | cl. 8.2 | — | — |
| M2d | DASH-IF push-based content ingest protocol | cl. 8.3 | — | — |
| M2d | HTTP low-latency pull-based content ingest protocol | cl. 8.4 | — | — |
| M3d | Server Certificates configuration API | cl. 9.2 | — | TS26512_Mas_Configuration_ServerCertificates.yaml |
| M3d | Content Preparation Templates configuration API | cl. 9.3 | — | TS26512_Mas_Configuration_ContentPreparationTemplates.yaml |
| M3d | Content Hosting configuration API | cl. 9.4 | — | TS26512_Mas_Configuration_ContentHosting.yaml |
| M4d | MPEG-DASH or 3GP-DASH or DASH-IF push-based content distribution | cl. 10.2 | — | — |
| M4d | HTTP low-latency content distribution | cl. 10.3 | — | — |
| M4d | In-band client data reporting (CMCD) (added in Release 19) | cl. 10.5 | — | — |
| M5d | Service Access Information API | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
| M10d | HTTP pull-based content ingest protocol (added in Release 19) | cl. 8.2 | — | — |
| M10d | DASH-IF push-based content ingest protocol (added in Release 19) | cl. 8.3 | — | — |
| M10d | HTTP low-latency pull-based content ingest protocol (added in Release 19) | cl. 8.4 | — | — |
Content publishing
Uplink · added in Release 16 · defined in TS 26.501 clause 4.0.3 · procedures in clause 6.2.3
Media content is published by the 5GMSu Client to a network-side component of the 5GMS System as part of an uplink session. It may be cached for a configurable period, and manipulated according to Content Preparation Templates. A provisioned Server Certificate may secure the content published.
Up to Release 17 · TS 26.512 V17.10.0, which specifies each API itself
| Reference point | API or protocol | TS 26.512 | OpenAPI file |
|---|---|---|---|
| M1u | Content Protocols Discovery API | cl. 7.5 | TS26512_M1_ContentProtocolsDiscovery.yaml |
TS 26.512 V17.10.0 table 5.2-1 has no content publishing row; for uplink it lists content protocols discovery only. The Content Publication Provisioning API (clause 7.6A) is listed from V18.7.0.
From Release 18 · TS 26.512 V19.3.0, which refers to TS 26.510 V19.2.0
| Reference point | API or protocol | TS 26.512 | TS 26.510 API (procedure) | OpenAPI file |
|---|---|---|---|---|
| M1u | Content Protocols Discovery API (listed in TS 26.512 as its own entry, content protocols discovery) | cl. 7.5 | cl. 8.3 (5.2.3) | TS26510_Maf_Provisioning_ContentProtocols.yaml |
| M1u | Provisioning Sessions API | cl. 7.2 | cl. 8.2 (5.2.2) | TS26510_Maf_Provisioning_ProvisioningSessions.yaml |
| M1u | Server Certificates Provisioning API | cl. 7.3 | cl. 8.4 (5.2.4) | TS26510_Maf_Provisioning_ServerCertificates.yaml |
| M1u | Content Preparation Templates Provisioning API | cl. 7.4 | cl. 8.5 (5.2.5) | TS26510_Maf_Provisioning_ContentPreparationTemplates.yaml |
| M1u | Content Publication Provisioning API | cl. 7.6A | cl. 8.9 (5.2.9) | TS26510_Maf_Provisioning_ContentPublishing.yaml |
| M2u | HTTP pull-based content egest protocol | cl. 8.5 | — | — |
| M2u | DASH-IF push-based content egest protocol | cl. 8.6 | — | — |
| M2u | HTTP low-latency pull-based content egest protocol | cl. 8.7 | — | — |
| M3u | Server Certificates configuration API | cl. 9.2 | — | TS26512_Mas_Configuration_ServerCertificates.yaml |
| M3u | Content Preparation Templates configuration API | cl. 9.3 | — | TS26512_Mas_Configuration_ContentPreparationTemplates.yaml |
| M3u | Content Publication configuration API | cl. 9.5 | — | TS26512_Mas_Configuration_ContentPublishing.yaml |
| M4u | DASH-IF push-based contribution protocol | cl. 10.4.2 | — | — |
| M5u | Service Access Information API | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
| M10u | HTTP pull-based content egest protocol (added in Release 19) | cl. 8.5 | — | — |
| M10u | DASH-IF push-based content egest protocol (added in Release 19) | cl. 8.6 | — | — |
| M10u | HTTP low-latency pull-based content egest protocol (added in Release 19) | cl. 8.7 | — | — |
Content preparation
Downlink and uplink · added in Release 16 · defined in TS 26.501 clause 4.0.4
Lets the Application Provider specify how network-side components manipulate content, according to provisioned Content Preparation Templates. It may include encoding, transcoding, packaging, encryption and protecting content with DRM. It is provisioned as part of content hosting (downlink) or content publishing (uplink). From Release 18, its APIs are the Content Preparation Templates rows of those two features. Up to Release 17, TS 26.512 lists the downlink API under content hosting and the uplink API as a feature of its own, below.
Up to Release 17 · TS 26.512 V17.10.0, which specifies each API itself
| Reference point | API or protocol | TS 26.512 | OpenAPI file |
|---|---|---|---|
| M1u | Content Preparation Templates Provisioning API | cl. 7.4 | TS26512_M1_ContentPreparationTemplatesProvisioning.yaml |
Network assistance
Downlink and uplink · added in Release 16 · defined in TS 26.501 clause 4.0.5 · procedures in clause 5.9 (d); 6.1, 6.5, 6.7 (u)
Lets the 5GMS Client interrogate or manipulate the network Quality of Service (QoS) of an ongoing session. It is not explicitly provisioned: whether it is available depends on system pre-configuration and policy. Two mechanisms: AF-based, through the PCF, and ANBR-based, between the UE modem and the RAN. Two sub-features: bit rate recommendation (throughput estimation), and delivery boost, a speculative request for a temporary boost to the session bit rate.
Up to Release 17 · TS 26.512 V17.10.0, which specifies each API itself
| Reference point | API or protocol | TS 26.512 | OpenAPI file |
|---|---|---|---|
| M5d | Service Access Information API | cl. 11.2 | TS26512_M5_ServiceAccessInformation.yaml |
| M5d | Network Assistance API | cl. 11.6 | TS26512_M5_NetworkAssistance.yaml |
| M5u | Service Access Information API | cl. 11.2 | TS26512_M5_ServiceAccessInformation.yaml |
| M5u | Network Assistance API | cl. 11.6 | TS26512_M5_NetworkAssistance.yaml |
From Release 18 · TS 26.512 V19.3.0, which refers to TS 26.510 V19.2.0
| Reference point | API or protocol | TS 26.512 | TS 26.510 API (procedure) | OpenAPI file |
|---|---|---|---|---|
| M5d | Service Access Information API | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
| M5d | Network Assistance API | cl. 11.6 | cl. 9.4 (5.3.4) | TS26510_Maf_SessionHandling_NetworkAssistance.yaml |
| M5u | Service Access Information API | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
| M5u | Network Assistance API | cl. 11.6 | cl. 9.4 (5.3.4) | TS26510_Maf_SessionHandling_NetworkAssistance.yaml |
Dynamic policies
Downlink and uplink · added in Release 16 · defined in TS 26.501 clause 4.0.6 · procedures in clause 5.8, 5.7.6 (d); 6.9 (u)
Lets the 5GMS Client manipulate the network traffic handling policies of an ongoing session. The Application Provider provisions Policy Templates within a Provisioning Session. Each Policy Template carries an External reference and the Network QoS parameters of one Service Operation Point (for example SD, HD or UHD), and may apply to one or more Data Networks or Network Slices. Media Entry Point documents refer to the same Service Operation Points in their Service Descriptions. Outside the trusted data network, the PCF is reached through the NEF.
Up to Release 17 · TS 26.512 V17.10.0, which specifies each API itself
| Reference point | API or protocol | TS 26.512 | OpenAPI file |
|---|---|---|---|
| M1d | Provisioning Sessions API | cl. 7.2 | TS26512_M1_ProvisioningSessions.yaml |
| M1d | Policy Templates Provisioning API | cl. 7.9 | TS26512_M1_PolicyTemplatesProvisioning.yaml |
| M5d | Service Access Information API | cl. 11.2 | TS26512_M5_ServiceAccessInformation.yaml |
| M5d | Dynamic Policies API | cl. 11.5 | TS26512_M5_DynamicPolicies.yaml |
| M1u | Provisioning Sessions API | cl. 7.2 | TS26512_M1_ProvisioningSessions.yaml |
| M1u | Policy Templates Provisioning API | cl. 7.9 | TS26512_M1_PolicyTemplatesProvisioning.yaml |
| M5u | Service Access Information API | cl. 11.2 | TS26512_M5_ServiceAccessInformation.yaml |
| M5u | Dynamic Policies API | cl. 11.5 | TS26512_M5_DynamicPolicies.yaml |
From Release 18 · TS 26.512 V19.3.0, which refers to TS 26.510 V19.2.0
| Reference point | API or protocol | TS 26.512 | TS 26.510 API (procedure) | OpenAPI file |
|---|---|---|---|---|
| M1d | Provisioning Sessions API | cl. 7.2 | cl. 8.2 (5.2.2) | TS26510_Maf_Provisioning_ProvisioningSessions.yaml |
| M1d | Policy Templates Provisioning API | cl. 7.9 | cl. 8.7 (5.2.7) | TS26510_Maf_Provisioning_PolicyTemplates.yaml |
| M5d | Service Access Information API | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
| M5d | Dynamic Policies API | cl. 11.5 | cl. 9, heading 9.3 (5.3.3) | TS26510_Maf_SessionHandling_DynamicPolicy.yaml |
| M1u | Provisioning Sessions API | cl. 7.2 | cl. 8.2 (5.2.2) | TS26510_Maf_Provisioning_ProvisioningSessions.yaml |
| M1u | Policy Templates Provisioning API | cl. 7.9 | cl. 8.7 (5.2.7) | TS26510_Maf_Provisioning_PolicyTemplates.yaml |
| M5u | Service Access Information API | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
| M5u | Dynamic Policies API | cl. 11.5 | cl. 9, heading 9.3 (5.3.3) | TS26510_Maf_SessionHandling_DynamicPolicy.yaml |
Remote control
Uplink · added in Release 16 · defined in TS 26.501 clause 4.0.7 · procedures in clause 6.6
High-level procedures for integrating remote control into 5GMS are in TS 26.501 clause 6.6. The feature is not further defined in this release, and TS 26.512 lists no APIs for it.
Consumption reporting
Downlink · added in Release 16 · defined in TS 26.501 clause 4.0.8 · procedures in clause 5.6
Media consumption in downlink sessions is logged and exposed for analysis. When provisioned, the 5GMSd Client reports consumption to a network-side component, and the data may be exposed as events to subscribing Application Providers. Downlink only in the current release.
Up to Release 17 · TS 26.512 V17.10.0, which specifies each API itself
| Reference point | API or protocol | TS 26.512 | OpenAPI file |
|---|---|---|---|
| M1d | Provisioning Sessions API | cl. 7.2 | TS26512_M1_ProvisioningSessions.yaml |
| M1d | Consumption Reporting Provisioning API | cl. 7.7 | TS26512_M1_ConsumptionReportingProvisioning.yaml |
| M5d | Service Access Information API | cl. 11.2 | TS26512_M5_ServiceAccessInformation.yaml |
| M5d | Consumption Reporting API | cl. 11.3 | TS26512_M5_ConsumptionReporting.yaml |
From Release 18 · TS 26.512 V19.3.0, which refers to TS 26.510 V19.2.0
| Reference point | API or protocol | TS 26.512 | TS 26.510 API (procedure) | OpenAPI file |
|---|---|---|---|---|
| M1d | Provisioning Sessions API | cl. 7.2 | cl. 8.2 (5.2.2) | TS26510_Maf_Provisioning_ProvisioningSessions.yaml |
| M1d | Consumption Reporting Provisioning API | cl. 7.7 | cl. 8.12 (5.2.12) | TS26510_Maf_Provisioning_ConsumptionReporting.yaml |
| M5d | Service Access Information API | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
| M5d | Consumption Reporting API | cl. 11.3 | cl. 9.6 (5.3.6) | TS26510_Maf_SessionHandling_ConsumptionReporting.yaml |
QoE metrics reporting
Downlink (see note) · added in Release 16 · defined in TS 26.501 clause 4.0.9 · procedures in clause 5.5
The Quality of Experience (QoE) of sessions is logged and exposed for analysis. Two mechanisms: RAN-based, with reports sent to the OAM via the RAN, and AF-based, with reports sent to network-side components of the 5GMS System. Data in AF-based reports may be exposed as events. TS 26.501 clause 4.0.9 limits the feature to downlink in the current release, while TS 26.512 table 5.2-1 lists uplink metrics reporting APIs and TS 26.501 clause 4.3.1 includes QoE metrics reporting at M5u; both are shown below. For uplink, TS 26.512 clause 7.8.1 adds that no standardised metrics schemes are defined for uplink media streaming.
Up to Release 17 · TS 26.512 V17.10.0, which specifies each API itself
| Reference point | API or protocol | TS 26.512 | OpenAPI file |
|---|---|---|---|
| M1d | Provisioning Sessions API | cl. 7.2 | TS26512_M1_ProvisioningSessions.yaml |
| M1d | Metrics Reporting Provisioning API | cl. 7.8 | TS26512_M1_MetricsReportingProvisioning.yaml |
| M5d | Service Access Information API | cl. 11.2 | TS26512_M5_ServiceAccessInformation.yaml |
| M5d | Metrics Reporting API | cl. 11.4 | TS26512_M5_MetricsReporting.yaml |
| M1u | Provisioning Sessions API | cl. 7.2 | TS26512_M1_ProvisioningSessions.yaml |
| M1u | Metrics Reporting Provisioning API | cl. 7.8 | TS26512_M1_MetricsReportingProvisioning.yaml |
| M5u | Service Access Information API | cl. 11.2 | TS26512_M5_ServiceAccessInformation.yaml |
| M5u | Metrics Reporting API | cl. 11.4 | TS26512_M5_MetricsReporting.yaml |
From Release 18 · TS 26.512 V19.3.0, which refers to TS 26.510 V19.2.0
| Reference point | API or protocol | TS 26.512 | TS 26.510 API (procedure) | OpenAPI file |
|---|---|---|---|---|
| M1d | Provisioning Sessions API | cl. 7.2 | cl. 8.2 (5.2.2) | TS26510_Maf_Provisioning_ProvisioningSessions.yaml |
| M1d | Metrics Reporting Provisioning API | cl. 7.8 | cl. 8.11 (5.2.11) | TS26510_Maf_Provisioning_MetricsReporting.yaml |
| M3d | Service Access Information API (added in Release 19) | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
| M3d | Metrics Reporting API (added in Release 19) | cl. 11.4 | cl. 9.5 (5.3.5) | TS26510_Maf_SessionHandling_MetricsReporting.yaml |
| M5d | Service Access Information API | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
| M5d | Metrics Reporting API | cl. 11.4 | cl. 9.5 (5.3.5) | TS26510_Maf_SessionHandling_MetricsReporting.yaml |
| M1u | Provisioning Sessions API | cl. 7.2 | cl. 8.2 (5.2.2) | TS26510_Maf_Provisioning_ProvisioningSessions.yaml |
| M1u | Metrics Reporting Provisioning API | cl. 7.8 | cl. 8.11 (5.2.11) | TS26510_Maf_Provisioning_MetricsReporting.yaml |
| M5u | Service Access Information API | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
| M5u | Metrics Reporting API | cl. 11.4 | cl. 9.5 (5.3.5) | TS26510_Maf_SessionHandling_MetricsReporting.yaml |
Edge processing
Downlink and uplink · added in Release 17 · defined in TS 26.501 clause 4.0.10 · procedures in clause 8
Lets the 5GMS Client use edge computing capabilities in the 5GMS System. Defined in TS 26.501 clause 4.5.
Up to Release 17 · TS 26.512 V17.10.0, which specifies each API itself
| Reference point | API or protocol | TS 26.512 | OpenAPI file |
|---|---|---|---|
| M1d | Provisioning Sessions API | cl. 7.2 | TS26512_M1_ProvisioningSessions.yaml |
| — | Edge Resources Provisioning API | cl. 7.10 | TS26512_M1_EdgeResourcesProvisioning.yaml |
| M5d | Service Access Information API | cl. 11.2 | TS26512_M5_ServiceAccessInformation.yaml |
| M1u | Provisioning Sessions API | cl. 7.2 | TS26512_M1_ProvisioningSessions.yaml |
| M1u | Edge Resources Provisioning API | cl. 7.10 | TS26512_M1_EdgeResourcesProvisioning.yaml |
| M5u | Service Access Information API | cl. 11.2 | TS26512_M5_ServiceAccessInformation.yaml |
TS 26.512 V17.10.0 table 4.2-1 leaves the reference point of the downlink Edge Resources Provisioning API row empty.
From Release 18 · TS 26.512 V19.3.0, which refers to TS 26.510 V19.2.0
| Reference point | API or protocol | TS 26.512 | TS 26.510 API (procedure) | OpenAPI file |
|---|---|---|---|---|
| M1d | Provisioning Sessions API | cl. 7.2 | cl. 8.2 (5.2.2) | TS26510_Maf_Provisioning_ProvisioningSessions.yaml |
| M1d | Edge Resources Provisioning API | cl. 7.10 | cl. 8.6 (5.2.6) | TS26510_Maf_Provisioning_EdgeResources.yaml |
| M5d | Service Access Information API | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
| M1u | Provisioning Sessions API | cl. 7.2 | cl. 8.2 (5.2.2) | TS26510_Maf_Provisioning_ProvisioningSessions.yaml |
| M1u | Edge Resources Provisioning API | cl. 7.10 | cl. 8.6 (5.2.6) | TS26510_Maf_Provisioning_EdgeResources.yaml |
| M5u | Service Access Information API | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
eMBMS delivery
Downlink · added in Release 17 · defined in TS 26.501 clause 4.0.11 · procedures in clause 5.10
The 5GMS System provisions the delivery of downlink content via eMBMS User Services sessions. Defined in TS 26.501 clause 4.6. TS 26.512 table 4.2-1 has two groups of 5GMS via eMBMS rows ("via eMBMS and MBMS User Services" and "via eMBMS"); they are merged below.
Up to Release 17 · TS 26.512 V17.10.0, which specifies each API itself
| Reference point | API or protocol | TS 26.512 | OpenAPI file |
|---|---|---|---|
| M1d | Provisioning Sessions API | cl. 7.2 | TS26512_M1_ProvisioningSessions.yaml |
| M5d | Service Access Information API | cl. 11.2 | TS26512_M5_ServiceAccessInformation.yaml |
| M4d | DASH or 3GP or HLS | cl. 10 | — |
From Release 18 · TS 26.512 V19.3.0, which refers to TS 26.510 V19.2.0
| Reference point | API or protocol | TS 26.512 | TS 26.510 API (procedure) | OpenAPI file |
|---|---|---|---|---|
| M1d | Provisioning Sessions API | cl. 7.2 | cl. 8.2 (5.2.2) | TS26510_Maf_Provisioning_ProvisioningSessions.yaml |
| M5d | Service Access Information API | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
| M4d | MPEG-DASH or 3GP-DASH or HLS | cl. 10 | — | — |
| M4d | MPEG-DASH or 3GP-DASH or HLS content distribution | cl. 10 | — | — |
Data collection, reporting and exposure
Downlink and uplink · added in Release 17 · defined in TS 26.501 clause 4.0.12 · procedures in clause 5.11 (d); 6.8 (u)
The 5GMS System logs data relating to media streaming sessions and exposes it to subscribers as events. Defined in TS 26.501 clause 4.7. In TS 26.512, data reporting at R4 is in clause 17 and event exposure at R5 and R6 in clause 18.
Up to Release 17 · TS 26.512 V17.10.0, which specifies each API itself
| Reference point | API or protocol | TS 26.512 | OpenAPI file |
|---|---|---|---|
| M1d | Event Data Processing Provisioning API | cl. 7.11 | TS26512_M1_EventDataProcessingProvisioning.yaml |
| R4 | Ndcaf_DataReporting service | cl. 17 | TS26512_R4_DataReporting.yaml |
| R5, R6 | Naf_EventExposure service | cl. 18 | — |
| M1u | Event Data processing Provisioning API | cl. 7.11 | TS26512_M1_EventDataProcessingProvisioning.yaml |
From Release 18 · TS 26.512 V19.3.0, which refers to TS 26.510 V19.2.0
| Reference point | API or protocol | TS 26.512 | TS 26.510 API (procedure) | OpenAPI file |
|---|---|---|---|---|
| M1d | Event Data Processing Provisioning API | cl. 7.11 | cl. 8.13 (5.2.13) | TS26510_Maf_Provisioning_EventDataProcessing.yaml |
| M1u | Event Data processing Provisioning API | cl. 7.11 | cl. 8.13 (5.2.13) | TS26510_Maf_Provisioning_EventDataProcessing.yaml |
| R4 | Ndcaf_DataReporting service | cl. 17 | — | TS26512_R4_DataReporting.yaml |
| R5, R6 | Naf_EventExposure service | cl. 18 | — | TS26512_EventExposure.yaml |
Service URL handling
Downlink and uplink · added in Release 18 · defined in TS 26.501 clause 4.0.13 · procedures in clause 9, 5.10.7 (d); 9 (u)
A 3GPP Service URL launches UE functions when it is executed. A 5GMS service can be announced in a third-party application, a web page, a messaging service or shared through social messages. When a service is launched with a 3GPP Service URL for 5GMS, a 5GMS Client function for media session handling is expected to launch alongside. Defined in TS 26.501 clause 4.10; the generic 3GPP Service URL is in TS 26.510 clause 6 and the 5GMS one in TS 26.512 clause 12.4.
MBS delivery
Downlink · added in Release 18 · defined in TS 26.501 clause 4.0.14 · procedures in clause 5.12
The 5GMS System provisions the delivery of downlink content via MBS User Services sessions. Defined in TS 26.501 clause 4.9.
From Release 18 · TS 26.512 V19.3.0, which refers to TS 26.510 V19.2.0
| Reference point | API or protocol | TS 26.512 | TS 26.510 API (procedure) | OpenAPI file |
|---|---|---|---|---|
| M1d | Provisioning Sessions API | cl. 7.2 | cl. 8.2 (5.2.2) | TS26510_Maf_Provisioning_ProvisioningSessions.yaml |
| M5d | Service Access Information API | cl. 11.2 | cl. 9.2 (5.3.2) | TS26510_Maf_SessionHandling_ServiceAccessInformation.yaml |
| M4d | MPEG-DASH or 3GP-DASH or HLS | cl. 10 | — | — |
Sources for this page
- The features: TS 26.501 V19.4.0, clauses 4.0.1 to 4.0.14 and table 4.0.1-1; "Added in" from the clause 4.0 feature lists of V16.15.0, V17.10.0, V18.9.0 and V19.4.0.
- Figures: redrawn from TS 26.501 V19.4.0, figures 4.0.2-1, 4.0.2-2, 4.0.3-1, 4.0.5-1, 4.0.6-1, 4.0.8-1 and 4.0.9-1.
- Feature by feature: TS 26.501 V19.4.0, clauses 4.0.2 to 4.0.14, 4.3.1 and 5.13; Up to Release 17, TS 26.512 V16.12.0 and V17.10.0, tables 4.2-1 and 5.2-1, and the OpenAPI files in the V17.10.0 archive. From Release 18, TS 26.512 V18.7.0 and V19.3.0, tables 4.2-1 and 5.2-1 and clauses 7, 9, 11, 12.4, 17 and 18; TS 26.510 V18.5.0 and V19.2.0, clauses 5.2, 5.3, 6, 8, 9 and 11; the OpenAPI files in the TS 26.510 V19.2.0 and TS 26.512 V19.3.0 archives.