A 5GMS Application Provider may request media processing to be performed on its media data. This can be instantiated as part of the Uplink or Downlink streaming. For uplink, FLUS TS 26.238
provides measures to describe the required media processing as part of the FLUS session creation request. For downlink media distribution, the 5GMSd Application Provider may wish to execute some media processing functions within the MNO network infrastructure.
The media processing is performed by a set of 5GMS AS(s), which may be combined together to build complex media processing workflows. A 5GMS AF coordinates the media processing and ensures that the appropriate QoS and traffic handling for the session are provided.
As part of setting up a Content Hosting Configuration for downlink media streaming, a 5GMSd Application Provider may request custom processing to be performed.
The following processing operations may be available:
Adaptive Bit Rate (ABR) Encoding, Encryption and Encapsulation.
MPD (e.g. MPD) Generator and Segment (e.g. DASH) Packager.
Content Replacement (e.g. Ad insertion, blackouts, regional content):
MPD (e.g. MPD) modification.
App Server: other content enrichment functions such as Closed Caption insertion, object detection, content filtering, etc.
The procedures are as follows:
The steps are as follows:
Upon setting up a Content Hosting Configuration, the 5GMSd Application Provider requests media processing to be set up. The 5GMSd Application Provider provides a description of the type and placement of the processing. The 5GMS System may only allow a shortlisted set of media processing functions to be used by the 5GMSd Application Provider.
The 5GMSd AF provisions a selected set of 5GMSd AS(s) to fulfil the requested media processing in the appropriate placement. Depending on the configuration, one or multiple AS(s) may be involved.
The 5GMSd AS(s) confirm successful provisioning to the 5GMSd AF.
The 5GMSd AF confirms the successful creation of the Content Hosting Configuration with the requested media processing to the external Media application server.
A 5GMSd Client sends a request for media content to one of the 5GMSd AS(s) listed in the provisioned Content Hosting Configuration (see clause 5.4
If it does not already have a copy of the requested media cached, the 5GMSd AS fetches the media from the 5GMSd Application Provider.
The 5GMSd AS processes the ingested media based on the provisioned media processing workflow.
The 5GMSd AS serves the requested media to the 5GMSd Client after successful media processing.
Different variants of these procedures may be possible, depending on the type of processing, the placement of the processing, and the characteristics of the Content Hosting Configuration.