A.1 Downlink media streaming with AS deployed in an external Data Network (OTT)

26.5013GPP5G Media Streaming (5GMS)General description and architectureRelease 18TS

The collaboration scenario shown in figure A.1-1 represents a typical OTT collaboration scenario, where only the 5GMSd AS is deployed and which resides in an external Data Network. In this collaboration scenario, neither the 5GMSd AF nor the Media Session Handler function of the 5GMSd Client is present/necessary for downlink media streaming operation. All Service Announcement Information is delivered at reference point M8d from the 5GMSd Application Provider to the 5GMSd-Aware Application. The latter then passes the Service Acess Information contained in the service announcement to the Media Player to enable downstream media streaming session establishment and media transfer. In addition, M8d is used for UE application-level data reporting from the 5GMSd Aware Application to the 5GMSd Application Provider. The Provisioning API (M1d′) and Ingest API (M2d′) may follow 5GMS specifications.

Figure A.1-1: Downlink media streaming with AF and AS in an external Data Network

The interfaces M1d′ and M2d′ may be similar to interfaces M1d and M2d respectively. Interface M4d follows 3GPP specifications.

NOTE: Although a single logical 5GMSd AS exposes both the M2d′ (Ingest) and M4d (Downlink Streaming) interfaces, these APIs may, in a real deployment, be implemented on different physical servers (with different FQDNs). Furthermore, a large number of serving nodes, each with its own FQDN may offer the M4d service, following CDN scaling principles.