8 Media Ingest and Publish (M2) protocols
26.5123GPP5G Media Streaming (5GMS)ProtocolsRelease 17TS
8.1 General
The set of content protocols supported by the 5GMS AS is listed in table 8.1-1 below:
Table 8.1-1: Supported content protocols
|
Description |
Term identifier |
Clause |
|---|---|---|
|
Content ingest protocols at interface M2d |
||
|
HTTP pull-based content ingest protocol |
urn:3gpp:5gms:content-protocol:http-pull-ingest |
8.2 |
|
DASH-IF push-based content ingest protocol |
urn:3gpp:5gms:content-protocol:dash-if-ingest |
8.3 |
|
Content egest protocols at interface M2u |
||
8.2 HTTP pull-based content ingest protocol
If IngestConfiguration.protocol is set to urn:3gpp:5gms:content-protocol:http-pull-ingest in the Content Hosting Configuration, media resources shall be ingested by the 5GMSd AS using HTTP [9]. The IngestConfiguration.pull property shall be set to True, indicating that a Pull-based protocol is used. The IngestConfiguration.baseURL property shall point at the 5GMSd Application Provider’s origin server, as specified in table 7.6.3.1‑1, and may indicate the use of HTTPS [16].
When the 5GMSd AS receives a request for a media resource at interface M4d that cannot be satisfied from its content cache, the request shall be transformed into a corresponding HTTP GET request directed to the 5GMSd Application Provider’s origin server via interface M2d as follows:
1. The prefix of the request URL indicated in the DistributionConfiguration.baseURL of the applicable Content Hosting Configuration is replaced with that of the corresponding IngestConfiguration.baseURL.
NOTE: It is the responsibility of the 5GMSd AF to assign unique M4d base URLs to each provisioned Content Hosting Configuration so as to ensure that this substitution is unambiguous.
2. The path rewrite rules (if provisioned in DistributionConfiguration.PathRewriteRules) are applied in strict order to the remainder of the request URL (i.e., the path segments following DistributionConfiguration.baseURL). The requestPathPattern of the first matching path rewrite rule is replaced with the corresponding mappedPath.
8.3 DASH-IF push-based content ingest protocol
If IngestConfiguration.protocol is set to urn:3gpp:5gms:content-protocol:dash-if-ingest in the Content Hosting Configuration, media resources shall be ingested by the 5GMSd AS as specified by the DASH‑IF Live Media Ingest specification [3]. The IngestConfiguration.pull property shall be set to False, indicating that a Push-based protocol is used. The IngestConfiguration.baseURL property shall be set by the 5GMSd AF to the base URL that is to be used by the 5GMSd Application Provider to upload the DASH segments and MPD(s) to the 5GMSd AS at reference point M2d.